Method and apparatus for configuring gap request and gaps for a terminal in wireless mobile communication system

ABSTRACT

A method and Apparatus for configuring gap request and gaps is provided. The method includes receiving from a base station a first RRCReconfiguration, receiving a second RRCReconfiguration, the second RRCReconfiguration includes a first gap configuration and a second gap configuration, establishing by the terminal a first gap or a second gap, Initiating RRC re-establishment procedure, releasing the first gap request configuration at a first point of time, and releasing the first gap configuration and the second gap configuration at a second point of time.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to and the benefit of Korean PatentApplication No. 10-2022-0050010, filed on Apr. 22, 2022, the disclosureof which is incorporated herein by reference in its entirety.

BACKGROUND

Technical Field

The present disclosure relates to configuring gap request and gaps for aterminal in wireless mobile communication system.

Related Art

To meet the increasing demand for wireless data traffic since thecommercialization of 4th generation (4G) communication systems, the 5thgeneration (5G) system is being developed. For the sake of high, 5Gsystem introduced millimeter wave (mmW) frequency bands (e.g. 60 GHzbands). In order to increase the propagation distance by mitigatingpropagation loss in the 5G communication system, various techniques areintroduced such as beamforming, massive multiple—input multiple output(MIMO), full dimensional MIMO (FD-MIMO), array antenna, analogbeamforming, and large-scale antenna. In addition, base station isdivided into a central unit and plurality of distribute units for betterscalability. To facilitate introduction of various services, 5Gcommunication system targets supporting higher data rate and smallerlatency.

As the uses of terminals diversify, the need to control the operation ofterminals by applying various gaps according to circumstances isemerging. For example, it is necessary to set a gap for measurement, agap for MUSIM operation, or a gap for transmission power control so thatthe operation of the terminal can proceed efficiently.

SUMMARY

Aspects of the present disclosure are to address the problems ofconfiguring gap request and gaps. In accordance with an aspect of thepresent disclosure, a method of a terminal in mobile communicationsystem comprises receiving from a base station a firstRRCReconfiguration, receiving a second RRCReconfiguration, the secondRRCReconfiguration includes a first gap configuration and a second gapconfiguration, establishing by the terminal a first gap or a second gap,Initiating RRC re-establishment procedure, releasing the first gaprequest configuration at a first point of time, and releasing the firstgap configuration and the second gap configuration at a second point oftime.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a diagram illustrating the architecture of an 5G system and aNG-RAN to which the disclosure may be applied.

FIG. 1B is a diagram illustrating a wireless protocol architecture in an5G system to which the disclosure may be applied.

FIG. 1C is a diagram illustrating an example of a bandwidth part.

FIG. 1D is a diagram illustrating an example of a search space and acontrol resource set.

FIG. 1E is a diagram illustrating various gaps.

FIG. 1F is a diagram illustrating gap patterns of various gaps.

FIG. 2 is a diagram illustrating operations of a terminal and a basestation according to an embodiment of the present invention.

FIG. 3 is a flow diagram illustrating an operation of a terminal.

FIG. 4A is a block diagram illustrating the internal structure of a UEto which the disclosure is applied.

FIG. 4B is a block diagram illustrating the configuration of a basestation according to the disclosure.

DETAILED DESCRIPTION

Hereinafter, embodiments of the present invention will be described indetail with reference to the accompanying drawings. In addition, in thedescription of the present invention, if it is determined that adetailed description of a related known function or configuration mayunnecessarily obscure the gist of the present invention, the detaileddescription thereof will be omitted. In addition, the terms to bedescribed later are terms defined in consideration of functions in thepresent invention, which may vary according to intentions or customs ofusers and operators. Therefore, the definition should be made based onthe content throughout this specification.

The terms used, in the following description, for indicating accessnodes, network entities, messages, interfaces between network entities,and diverse identity information is provided for convenience ofexplanation. Accordingly, the terms used in the following descriptionare not limited to specific meanings but may be replaced by other termsequivalent in technical meanings.

In the following descriptions, the terms and definitions given in the3GPP standards are used for convenience of explanation. However, thepresent disclosure is not limited by use of these terms and definitionsand other arbitrary terms and definitions may be employed instead.

Table 1 lists the acronyms used throughout the present disclosure.

TABLE 1 Acronym Full name Acronym Full name 5GC 5G Core Network RACHRandom Access Channel ACK Acknowledgement RAN Radio Access Network AMAcknowledged Mode RAR Random Access Response AMF Access and MobilityRA-RNTI Random Access RNTI Management Function ARQ Automatic RepeatRequest RAT Radio Access Technology AS Access Stratum RB Radio BearerASN.1 Abstract Syntax Notation RLC Radio Link Control One BSR BufferStatus Report RNA RAN-based Notification Area BWP Bandwidth Part RNAURAN-based Notification Area Update CA Carrier Aggregation RNTI RadioNetwork Temporary Identifier CAG Closed Access Group RRC Radio ResourceControl CG Cell Group RRM Radio Resource Management C-RNTI Cell RNTIRSRP Reference Signal Received Power CSI Channel State Information RSRQReference Signal Received Quality DCI Downlink Control RSSI ReceivedSignal Strength Information Indicator DRB (user) Data Radio Bearer SCellSecondary Cell DRX Discontinuous Reception SCS Subcarrier Spacing HARQHybrid Automatic Repeat SDAP Service Data Adaptation Request Protocol IEInformation element SDU Service Data Unit LCG Logical Channel Group SFNSystem Frame Number MAC Medium Access Control S-GW Serving Gateway MIBMaster Information Block SI System Information NAS Non-Access StratumSIB System Information Block NG-RAN NG Radio Access Network SpCellSpecial Cell NR NR Radio Access SRB Signalling Radio Bearer PBRPrioritised Bit Rate SRS Sounding Reference Signal PCell Primary Cell SSSearch Space PCI Physical Cell Identifier SSB SS/PBCH block PDCCHPhysical Downlink Control SSS Secondary Synchronisation Channel SignalPDCP Packet Data Convergence SUL Supplementary Uplink Protocol PDSCHPhysical Downlink Shared TM Transparent Mode Channel PDU Protocol DataUnit UCI Uplink Control Information PHR Power Headroom Report UE UserEquipment PLMN Public Land Mobile Network UM Unacknowledged Mode PRACHPhysical Random Access CRP Cell Reselection Priority Channel PRBPhysical Resource Block PSS Primary Synchronisation Signal PUCCHPhysical Uplink Control Channel PUSCH Physical Uplink Shared Channel

Table 2 lists the terminologies and their definition used throughout thepresent disclosure.

TABLE 2 Terminology Definition Carrier frequency center frequency of thecell. Cell combination of downlink and optionally uplink resources. Thelinking between the carrier frequency of the downlink resources and thecarrier frequency of the uplink resources is indicated in the systeminformation transmitted on the downlink resources. Cell Group in dualconnectivity, a group of serving cells associated with either the MeNBor the SeNB. Cell reselection A process to find a better suitable cellthan the current serving cell based on the system information receivedin the current serving cell Cell selection A process to find a suitablecell either blindly or based on the stored information Cell ReselectionPriority of a carrier frequency regarding cell reselection. SystemPriority Information Block 2 and System Information Block 3 provide theCRP of the serving frequency and CRPs of inter-frequencies respectively.UE consider higher priority frequency for cell reselection if channelcondition of the frequency is better than a specific threshold even ifchannel condition of a lower priority frequency is better than that ofthe higher priority frequency. Dedicated Signalling sent on DCCH logicalchannel between the network and signalling a single UE. Field Theindividual contents of an information element are referred to as fields.Frequency layer set of cells with the same carrier frequency. Globalcell An identity to uniquely identifying an NR cell. It is consisted ofidentity cellIdentity and plmn-Identity of the first PLMN-Identity inplmn- IdentityList in SIB1. gNB node providing NR user plane and controlplane protocol terminations towards the UE, and connected via the NGinterface to the 5GC. Handover procedure that changes the serving cellof a UE in RRC_CONNECTED. Information A structural element containingsingle or multiple fields is referred element as information element. LThe Length field in MAC subheader indicates the length of thecorresponding MAC SDU or of the corresponding MAC CE LCID 6 bit logicalchannel identity in MAC subheader to denote which logical channeltraffic or which MAC CE is included in the MAC subPDU Logical channel alogical path between a RLC entity and a MAC entity. There are multiplelogical channel types depending on what type of information istransferred e.g. CCCH (Common Control Channel), DCCH (Dedicate ControlChannel), DTCH (Dedicate Traffic Channel), PCCH (Paging Control Channel)NR NR radio access PCell SpCell of a master cell group. registered PLMNPLMN which UE has registered to selected PLMN PLMN which UE has selectedto perform registration procedure equivalent PLMN PLMN which isequivalent to registered PLMN. UE is informed of list of EPLMNs by AMFduring registration procedure PLMN ID Check the process that checkswhether a PLMN ID is the RPLMN identity or an EPLMN identity of the UE.Primary Cell The MCG cell, operating on the primary frequency, in whichthe UE either performs the initial connection establishment procedure orinitiates the connection re-establishment procedure. Radio BearerLogical path between a PDCP entity and upper layer (i.e. SDAP entity orRRC) RLC bearer RLC and MAC logical channel configuration of a radiobearer in one cell group. RLC bearer The lower layer part of the radiobearer configuration comprising configuration the RLC and logicalchannel configurations. Serving Cell For a UE in RRC_CONNECTED notconfigured with CA/DC there is only one serving cell comprising of theprimary cell. For a UE in RRC_CONNECTED configured with CA/DC the term‘serving cells’ is used to denote the set of cells comprising of theSpecial Cell(s) and all secondary cells. SpCell primary cell of a masteror secondary cell group. Special Cell For Dual Connectivity operationthe term Special Cell refers to the PCell of the MCG or the PSCell ofthe SCG, otherwise the term Special Cell refers to the PCell. SRBSignalling Radio Bearers” (SRBs) are defined as Radio Bearers (RBs) thatare used only for the transmission of RRC and NAS messages. SRB0 SRB0 isfor RRC messages using the CCCH logical channel SRB1 SRB1 is for RRCmessages (which may include a piggybacked NAS message) as well as forNAS messages prior to the establishment of SRB2, all using DCCH logicalchannel; SRB2 SRB2 is for NAS messages and for RRC messages whichinclude logged measurement information, all using DCCH logical channel.SRB2 has a lower priority than SRB1 and may be configured by the networkafter AS security activation; SRB3 SRB3 is for specific RRC messageswhen UE is in (NG)EN-DC or NR-DC, all using DCCH logical channel SRB4SRB4 is for RRC messages which include application layer measurementreporting information, all using DCCH logical channel. DCCH DCCH is alogical channel to transfer RRC messages after RRC connectionestablishment Suitable cell A cell on which a UE may camp. Followingcriteria apply The cell is part of either the selected PLMN or theregistered PLMN or PLMN of the Equivalent PLMN list The cell is notbarred The cell is part of at least one TA that is not part of the listof “Forbidden Tracking Areas for Roaming” (TS 22.011 [18]), whichbelongs to a PLMN that fulfils the first bullet above. The cellselection criterion S is fulfilled (i.e. RSRP and RSRQ are better thanspecific values

In the present invention, “trigger” or “triggered” and “initiate” or“initiated” may be used in the same meaning.

FIG. 1A is a diagram illustrating the architecture of an 5G system and aNG-RAN to which the disclosure may be applied.

5G system consists of NG-RAN 1A-01 and 5GC 1A-02. An NG-RAN node iseither:

-   -   a gNB, providing NR user plane and control plane protocol        terminations towards the UE; or    -   an ng-eNB, providing E-UTRA user plane and control plane        protocol terminations towards the UE.

The gNBs 1A-05 or 1A-06 and ng-eNBs 1A-03 or 1A-04 are interconnectedwith each other by means of the Xn interface. The gNBs and ng-eNBs arealso connected by means of the NG interfaces to the 5GC, morespecifically to the AMF (Access and Mobility Management Function) and tothe UPF (User Plane Function). AMF 1A-07 and UPF 1A-08 may be realizedas a physical node or as separate physical nodes.

A gNB 1A-05 or 1A-06 or an ng-eNBs 1A-03 or 1A-04 hosts the functionslisted below.

Functions for Radio Resource Management such as Radio Bearer Control,Radio Admission Control, Connection Mobility Control, Dynamic allocationof resources to UEs in uplink, downlink and sidelink(scheduling); and

IP and Ethernet header compression, uplink data decompression andencryption of user data stream; and

Selection of an AMF at UE attachment when no routing to an MME can bedetermined from the information provided by the UE; and

Routing of User Plane data towards UPF; and

Scheduling and transmission of paging messages; and

Scheduling and transmission of broadcast information (originated fromthe AMF or O&M); and

Measurement and measurement reporting configuration for mobility andscheduling; and

Session Management; and

QoS Flow management and mapping to data radio bearers; and

Support of UEs in RRC_INACTIVE state; and

Radio access network sharing; and

Tight interworking between NR and E-UTRA; and

Support of Network Slicing.

The AMF 1A-07 hosts the functions such as NAS signaling, NAS signalingsecurity, AS security control, SMF selection, Authentication, Mobilitymanagement and positioning management.

The UPF 1A-08 hosts the functions such as packet routing and forwarding,transport level packet marking in the uplink, QoS handling and thedownlink, mobility anchoring for mobility etc.

FIG. 1B is a diagram illustrating a wireless protocol architecture in an5G system to which the disclosure may be applied.

User plane protocol stack consists of SDAP 1B-01 or 1B-02, PDCP 1B-03 or1B-04, RLC 1B-05 or 1B-06, MAC 1B-07 or 1B-08 and PHY 1B-09 or 1B-10.Control plane protocol stack consists of NAS 1B-11 or 1B-12, RRC 1B-13or 1B-14, PDCP, RLC, MAC and PHY.

Each protocol sublayer performs functions related to the operationslisted in the table 3.

TABLE 3 Sublayer Functions NAS authentication, mobility management,security control etc RRC System Information, Paging, Establishment,maintenance and release of an RRC connection, Security functions,Establishment, configuration, maintenance and release of SignallingRadio Bearers (SRBs) and Data Radio Bearers (DRBs), Mobility, QoSmanagement, Detection of and recovery from radio link failure, NASmessage transfer etc. SDAP Mapping between a QoS flow and a data radiobearer, Marking QoS flow ID (QFI) in both DL and UL packets. PDCPTransfer of data, Header compression and decompression, Ciphering anddeciphering, Integrity protection and integrity verification,Duplication, Reordering and in-order delivery, Out-of-order deliveryetc. RLC Transfer of upper layer PDUs, Error Correction through ARQ,Segmentation and re-segmentation of RLC SDUs, Reassembly of SDU, RLCre-establishment etc. MAC Mapping between logical channels and transportchannels, Multiplexing/demultiplexing of MAC SDUs belonging to one ordifferent logical channels into/from transport blocks (TB) deliveredto/from the physical layer on transport channels, Scheduling informationreporting, Priority handling between UEs, Priority handling betweenlogical channels of one UE etc. PHY Channel coding, Physical-layerhybrid-ARQ processing, Rate matching, Scrambling, Modulation, Layermapping, Downlink Control Information, Uplink Control Information etc.

FIG. 1C is a diagram illustrating an example of a bandwidth part.

With Bandwidth Adaptation (BA), the receive and transmit bandwidth of aUE need not be as large as the bandwidth of the cell and can beadjusted: the width can be ordered to change (e.g. to shrink duringperiod of low activity to save power); the location can move in thefrequency domain (e.g. to increase scheduling flexibility); and thesubcarrier spacing can be ordered to change (e.g. to allow differentservices). A subset of the total cell bandwidth of a cell is referred toas a Bandwidth Part (BWP) and BA is achieved by configuring the UE withBWP(s) and telling the UE which of the configured BWPs is currently theactive one. set.

FIG. 1C describes a scenario where 3 different BWPs are configured:

-   -   BWP1 with a width of 40 MHz and subcarrier spacing of 15 kHz;        1C-11 or 1C-19    -   BWP2 with a width of 10 MHz and subcarrier spacing of 15 kHz;        1C-13 or 1C-17    -   BWP3 with a width of 20 MHz and subcarrier spacing of 60 kHz.        1C-15

FIG. 1D is a diagram illustrating an example of a search space and acontrol resource set.

A plurality of SSs may be configured in one BWP. The UE monitors PDCCHcandidates according to the SS configuration of the currently activatedBWP. One SS consists of an SS identifier, a CORESET identifierindicating the associated CORESET, the period and offset of the slot tobe monitored, the slot unit duration, the symbol to be monitored in theslot, the SS type, and the like. The information may be explicitly andindividually configured or may be configured by a predetermined indexrelated to predetermined values.

One CORESET consists of a CORESET identifier, frequency domain resourceinformation, symbol unit duration, TCI status information, and the like.

Basically, it can be understood that CORESET provides frequency domaininformation to be monitored by the UE, and SS provides time domaininformation to be monitored by the UE.

CORESET#0 and SS#0 may be configured in the IBWP. One CORESET and aplurality of SSs may be additionally configured in the IBWP. Uponreceiving the MIB 1D-01, the UE recognizes CORESET #0 1D-02 and SS#01D-03 for receiving SIB1 using predetermined information included in theMIB. The UE receives SIB1 1D-05 through CORESET #0 1D-02 and SS#0 1D-03.In SIB 1, information constituting CORESET#01D-06 and SS#01D-07 andinformation constituting another CORESET, for example, CORESET#n1D-11and SS#m1D-13 may be included.

The terminal receives necessary information from the base station beforethe terminal enters the RRC_CONNECTED state, such as SIB2 reception,paging reception, and random access response message reception by usingthe CORESETs and SSs configured in SIB 1. CORESET #0 1D-02 configured inMIB and CORESET #0 1D-06 configured in SIB1 may be different from eachother, and the former is called a first CORESET #0 and the latter iscalled a second CORESET #0. SS#0 1D-03 configured in MIB and SS#0 1D-07configured in SIB 1 may be different from each other, and the former isreferred to as a first SS#0 and the latter is referred to as a secondSS#0. SS#0 and CORESET#0 configured for the RedCap terminal are referredto as a third SS#0 and a third CORESET#0. The first SS#0, the secondSS#0, and the third SS#0 may be the same as or different from eachother. The first CORESET#0, the second CORESET#0, and the thirdCORESET#0 may be the same as or different from each other. SS#0 andCORESET#0 are each indicated by a 4-bit index. The 4-bit index indicatesa configuration predetermined in the standard specification. Except forSS#0 and CORESET#0, the detailed configuration of the remaining SS andCORSESET is indicated by each individual information element.

When the RRC connection is established, additional BWPs may beconfigured for the UE.

A Serving Cell may be configured with one or multiple BWPs.

UE can be configured with one or more DL BWPs and one or more UL BWPs ina serving cell. If the serving cell operates in paired spectrum (i.e.,FDD band), the number of DL BWPs and the number of UL BWPs can bedifferent. If the serving cell operates in unpaired spectrum (i.e., TDDband), the number of DL BWPs and the number of UL BWPs is same.

SIB1 includes a DownlinkConfigCommonSIB and a UplinkConfigCommonSIB anda tdd-UL-DL-ConfigurationCommon.

TDD-UL-DL-ConfigurationCommon is cell specific TDD UL/DL configuration.It consists of subfields such as referenceSubcarrierSpacing, pattern1,and pattern2.

ReferenceSubcarrierSpacing is the reference SCS used to determine thetime domain boundary in the UL-DL pattern.

Pattern1 and pattern2 are TDD Uplink Downlink Pattern. It consists ofsubfields such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots,nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols.

DL-UL-TransmissionPeriodicity indicates the period of the DL-UL pattern.NRofDownlinkSlots indicates the number of consecutive full DL slots ineach DL-UL pattern.

NRofDownlinkSymbols indicates the number of consecutive DL symbols fromthe beginning of the slot following the last full DL slot.

NRofUplinkSlots indicates the number of consecutive full UL slots ineach DL-UL pattern.

NRofUplinkSymbols indicates the number of consecutive UL symbols at thelast time point of a slot preceding the first full UL slot.

Slots between the last full DL slot and the first full UL slot areflexible slots. full UL slot is also called static UL slot. UL slot inthis disclosure is static UL slot.

DownlinkConfigCommonSIB includes BWP-DownlinkCommon IE for initial DLBWP. UplinkConfigCommonSIB includes BWP-UplinkCommon IE for initial ULBWP. BWP-id of initialDownlinkBWP is 0.

A RRCReconfiguration message includes one or more BWP-Downlink and oneor more BWP-Uplink and a firstActiveDownlinkBWP-Id and abwp-InactivityTimer and a defaultDownlinkBWP-Id and aBWP-DownlinkDedicated for the initial DL BWP.

A BWP-Downlink IE includes a bwp-Id and a BWP-DownlinkCommon and aBWP-DownlinkDedicated.

A BWP-Uplink IE includes a bwp-Id and a BWP-UplinkCommon and aBWP-UplinkDedicated.

The bwp-Id is an integer between 0 and 4. bwp-Id 0 is used only for theBWP indicated in SIB 1. bwp-Id1-4 can be used for the BWPs indicated inthe RRCReconfiguration message.

BWP-DownlinkCommon IE includes following information: Frequency domainlocation and bandwidth of this bandwidth part, subcarrier spacing to beused in this BWP, cell specific parameters for the PDCCH of this BWP,cell specific parameters for the PDSCH of this BWP.

BWP-UplinkCommon IE includes following information: Frequency domainlocation and bandwidth of this bandwidth part, subcarrier spacing to beused in this BWP, cell specific parameters for the PUCCH of this BWP,cell specific parameters for the PUSCH of this BWP, Configuration ofcell specific random access parameters.

BWP-DownlinkDedicated is used to configure the dedicated (UE specific)parameters of a downlink BWP. It includes cell specific parameters forthe PDCCH of this BWP, cell specific parameters for the PDSCH of thisBWP It includes Type2GapStatus. Type2GapStatus IE is enumerated with asingle value of “deactivated”. Alternatively, Type2GapStatus IE isenumerated with a single value of “activated”. Alternatively,Type2GapStatus IE is enumerated with two values of “deactivated” and“activated”. Alternatively, Type2GapStatus IE includes an DL BWP-Id.

The BWP-UplinkDedicated is used to configure the dedicated (UE specific)parameters of an uplink BWP.

FirstActiveDownlinkBWP-Id contains the ID of the DL BWP to be activatedupon performing the RRC (re-)configuration.

DefaultDownlinkBWP-Id is the ID of the downlink bandwidth part to beused upon expiry of the BWP inactivity timer.

BWP-InactivityTimer is the duration in ms after which the UE falls backto the default Bandwidth Part

RRCReconfiguration message includes one or more SCellConfig IEs. ASCellConfig IE is used to configure a secondary cell. A SCellConfig IEcan includes a serving cell index and a serving cell configuration and asCellDeactivationTimer

FIG. 1E is a diagram illustrating various gaps.

In this disclosure six gaps are defined: Type1Gap, Type2Gap, Type3Gap,Type4Gap, Type5Gap and Type6Gap.

Type1Gap is used for RRM measurement on all FR1 frequencies or on allFR2 frequencies or on all frequencies. Type1Gap is always activated onceit is configured. During a Type1Gap 1E-03, UE performs gap operation 1.

Type2Gap is used for RRM measurement on all frequencies. Type2Gap isactivated only when an associated BWP is activated (or deactivated).During a Type2Gap 1E-03, UE performs gap operation1-1. A Type2Gap can becalled preconfigured gap.

Type3Gap is used for RRM measurement on specific frequency (orfrequencies). Type3Gap is always activated once it is configured. Duringa Type3Gap 1E-03, UE performs gap operation1-1. A Type3Gap can be calledconcurrent gap. A type3Gap is associated with a frequency if the ID ofthe type3Gap is indicated in the measurement object of the frequency.

One or more type3Gaps can be associated with a measurement object (i.e.a configuration information for a measurement object can includes aplurality of measGapId(s)) . In this case, the plurality of type3Gapsare used simultaneously for measurement on the frequency associated withthe measurement object. It is useful in circumstances where adjacentneighboring cells are not synchronized with each other.

Type4Gap is used for RRM measurement on all FR1 frequencies or on allFR2 frequencies or on all frequencies. UE performs data activity likeDL-SCH reception during Type4Gap. A Type4Gap 1E-05 consists of twointerruption periods 1E-09) and one measurement period 1E-07. During theinterruption periods, UE performs gap operation 2. During themeasurement period 1E-07, UE performs gap operation 3. A Type4Gap can becalled NCSG (Network Controlled Small Gap).

Type5Gap is used for activity in the other USIM. During a Type5Gap1E-11, UE performs gap operation4. A Type5Gap can be called MUSIM Gap.

Type6Gap is used for power management. During a Type6Gap 1E-13, UEperforms gap operation6. Type6Gap starts with an UL slot. UE determinesthe UL slot based on the tdd-UL-DL-ConfigurationCommon.

FIG. 1F is a diagram illustrating gap patterns of various gaps.

Type1Gap and Type3Gap and Type4Gap and Type6Gap are periodicallyoccurring once they are configured. Type2Gap is periodically occurringonce configured and activated. Type5Gap is either periodically occurringor aperiodically occurring once configured.

The pattern of periodic gaps is controlled by an offset parameter and agap repetition period parameter and a gap length parameter. For example,when offset is 24 and gap repetition period is 40 ms and gap length is 4ms, the first gap 1F-11 occurs at subframe #4 of SFN 22 and continues 4msec. The second gap 1F-13 occurs at subframe #4 of SFN 25 and continues4 msec and so on.

The pattern of aperiodic gaps is controlled by offset parameter and gaprepetition period parameter and gap length parameter and gap numberparameter. For example, when offset is 5220 and gap repetition period is64 ms and gap length is 32 ms, the first gap 1F-15 occurs at subframe #0of SFN 522 and continues 32 msec. The second gap 1F-17 occurs atsubframe #4 of SFN 528 and continues 32 msec. Since gap number is 2,only two gaps occur.

To configure Type1Gap or Type2Gap or Type3Gap or Type4Gap, MeasGapConfigIE is used. MeasGapConfig IE is included in MeasConfig IE. MeasConfig IEis included in RRCReconfiguration message.

MeasGapConfig IE may include a gapFR2 field and a gapFR1 field and agapUE field and a gapBwpToRemoveList field and a gapBwpToAddModListfield and a gapUEToAddModList field and a gapFR2ToAddModList field and agapFR1ToAddModList field.

GapFR2 field is included in the non-extended part of MeasGapConfig IE.gapFR1 field and gapUE IE are included in the first extended part ofMeasGapConfig IE. gapBwpToRemoveList and gapBwpToAddModList andgapFRorUEToRemoveList and gapUEToAddModList and a gapFR2ToAddModListfield and a gapFR1ToAddModList field are included in the second extendedpart of MeasGapConfig IE.

GapFR1 field and gapFR2 field and gapUE field are used to configureType1Gap or Type4Gap. gapFR1 field and gapFR2 field and gapUE field caninclude GapConfig IE.

GapOffset and mgl and mgrp and mgta are included in the non-extendedpart of GapConfig IE.

RefServCellIndicator can be included in the first extended part ofGapConfig IE.

RefFR2ServCellAsyncCA and mgl2 are included in the second extended partof GapConfig IE.

Type2Indicator and type4Indicatorare included in the third extended partof GapConfig IE.

GapUEToRemoveList and gapUEToAddModList and gapFR2ToAddModList and agapFR1ToAddModList and gapFR2ToRemoveList and gapFR1ToRemoveList areused to configure or release Type2Gap or Type3Gap or Type4Gap.

To configure Type5Gap, Musim-GapConfig IE is used. Musim-GapConfig IE isincluded in RRCReconfiguration message.

Musim-GapConfig IE can includes musim-GapConfigToRemoveList andmusim-GapConfigToAddModList. musim-GapConfigToAddModList consist ofplurality of musim-GapConfigToAddMod.

To configure Type6Gap, Type6GapConfig IE is used. Type6GapConfig IE isincluded in RRCReconfiguration message.

FIG. 2 is a diagram illustrating the operations for gap configuration.

In 2A-11, UE transmits GNB UECapabilityInformation message.UECapabilityInformation message includes following gap relatedcapability information: gap-request-capability-information,gap-configuration-capability-information.

Gap-request-capability-information includes following information:NeedForGap-Reporting, musim-NeedForGap-Reporting

UE can request Type1Gap and Type2Gap and Type3Gap and Type4Gap bytransmitting either RRCReconfigurationComplete message orRRCResumeComplete message or LocationMeasurementInfo.

UE can request Type5Gap by transmitting UEAssistanceInformation.

For UE to request gap by transmitting RRCReconfigurationComplete orRRCResumeComplete or UEAssistanceInformation, GNB needs to configure UEto request gap. GNB determines it based on reported capability. UE canrequest gap by LocationMeasurementInfo without any prior configuration.

NeedForGap-Reporting indicates whether the UE supports reporting themeasurement gap requirement information for NR target in the UE responseto a network configuration RRC message. It is enumerated with a singlevalue of “support”. It is per UE capability. A single IE can be presentin UECapability for NR. Absence of the IE indicates the feature is notsupported by the UE. Presence of the IE indicates the feature issupported by the UE in FR1 and in FR2 and in FDD and in TDD.

Musim-NeedForGap-Reporting indicates whether the UE supports reportingthe gap requirement information for MUSIM. It is enumerated with asingle value of “support”. It is per UE capability. A single IE can bepresent in UECapability for NR. Absence of the IE indicates the featureis not supported by the UE. Presence of the IE indicates the feature issupported by the UE in FR1 and in FR2 and in FDD and in TDD.

NeedForGap-Reporting indicates the capability related to type1Gap andtype2Gap and type3Gap and type4Gap. If NeedForGap-Reporting andsupportType2Gap are reported, UE supports reporting the measurement gaprequirement information for Type2Gap. If NeedForGap-Reporting andsupportType4Gapare reported, UE supports reporting the measurement gaprequirement information for Type4Gap. If NeedForGap-Reporting isreported, UE supports reporting the measurement gap requirements forType1Gap and Type3Gap.

UE does not report capability on whether the UE support reporting themeasurement gap requirement information in the UE initiated RRC message(i.e., LocationMeasurementInfo).

Gap-configuration-capability-information includes following information:supportedGapPattern, supportType2Gap, supportType4Gap, supportType5Gap,supportType6Gap and supportedGapCombination.

SupportedGapPattern indicates measurement gap pattern(s) optionallysupported by the UE. It is a bit string with 22 bits. Theleading/leftmost bit (bit 0) corresponds to the gap pattern 2, the nextbit corresponds to the gap pattern 3 and so on. A gap pattern is definedby a Gap Length and a Repetition Period. It is per UE capability. Thesupported gap patterns are supported by the UE in FR1 and in FR2 and inFDD and in TDD.

SupportType2Gap indicates whether the UE supports Type2Gap (i.e., gapactivated and deactivated depending on which BWP is activated; DL BWPdependent gap). It is per band capability. One or more IEs can bepresent in UECapability for NR. Absence of the IE in a band informationindicates the feature is not supported by the UE in the correspondingband. Presence of the IE indicates the feature is supported by the UE inthe corresponding band.

Alternatively, it can be per UE capability. In this case, a single IEcan be present in UECapability for NR. Absence of the IE indicates thefeature is not supported by the UE. Presence of the IE indicates thefeature is supported by the UE in FR1 and in FDD and in TDD. To indicatewhether UE support Type2Gap in FR2, additional capability information isused.

SupportType4Gap indicates whether the UE supports Type4Gap (i.e., gapconsists of interruption period and measurement period; gap whereinterruption on data activity occurs in the beginning of a gap and inthe end of a gap; gap where measurement is performed withoutinterruption on data activity in the middle of the gap). It is per bandcapability. One or more IEs can be present in UECapability for NR.Absence of the IE in a band information indicates the feature is notsupported by the UE in the corresponding band. Presence of the IEindicates the feature is supported by the UE in the corresponding band.

Alternatively, it can be per UE capability. In this case, a single IEcan be present in UECapability for NR. Absence of the IE indicates thefeature is not supported by the UE. Presence of the IE indicates thefeature is supported by the UE in FR1 and in FR2 and in FDD and in TDD.

SupportType5Gap indicates whether the UE supports Type5Gap.Alternatively, it indicates whether UE supports MUSIM assistanceinformation reporting. It is per UE capability. A single IE can bepresent in UECapability for NR. Absence of the IE indicates the featureis not supported by the UE. Presence of the IE indicates the feature issupported by the UE in FR1 and in FR2 and in FDD and in TDD.

SupportType6Gap indicates whether the UE supports Type6Gap. It is per FRcapability. two IEs can be present in UECapability for NR. Absence ofthe IE for FR2 indicates the feature is not supported by the UE in theFR2. Presence of the IE for FR2 indicates the feature is supported bythe UE in the FR and in TDD. Presence of the IE for FR1 indicates thefeature is supported by the UE in the FR and in TDD and in FDD.

SupportedGapCombination indicates gap combinations supported by the UEamong predefined gap combinations. It is a bit string with a predefinedsize. The predefined size is equal to the number of predefined gapcombinations optionally supported. The leading/leftmost bit (bit 0)corresponds to the optional gap combination with the lowest index, thenext bit corresponds to the optional gap combination with the nextlowest index and so on.

A gap combination consists of gap combination identifier (or index) andnumber of per-FR1 gaps and number of per-FR2 gaps and number of per-UEgaps. This IE indicates the number of measurement gaps simultaneouslysupported by the UE. It is per UE capability. The supported gapcombinations are supported by the UE in FR1 and in FR2 and in FDD and inTDD.

A gap combination consists of gap combination identifier (or index) andnumber of per-FR1 gaps and number of per-FR2 gaps and number of per-UEgaps. Among the predefined gap combinations, some predefined gapcombinations are mandatorily supported by the UE. Some predefined gapcombinations are optionally supported by the UE. supportedGapCombinationindicates which optional gap combinations are supported by the UE.

Example is shown in the table below. The range of the integer is between0 and 2 (i.e., the highest value is 2 and the lowest value is 0; themaximum number of simultaneous gaps per FR is 2).

TABLE 4 # of simultaneous MG Index Per-FR1 Per-FR2 Per-UE . . . . . . .. . . . . n integer 1 integer2 integer3 n + 1 integer4 integer5 integer6. . . . . . . . . . . .

Based on reported UE capabilities, GNB determines configurations to beapplied to the UE.

BWP-SwitchingDelay defines whether the UE supports DCI and timer basedactive BWP switching delay type1 or type2. It indicates one of type1 andtype2. It is per UE capability. The indicated bwp-SwitchingDelay issupported by the UE in FR1 and in FR2 and in FDD and in TDD.

In 2A-13, GNB transmits UE first RRC message. first RRC message includesconfiguration information for gap request. Configuration information forgap request includes one of followings: needForGapsConfigNR,needForGapsConfigNR2, needForGapsConfigNR3, musim-AssistanceConfig andneedFortype6GapConfig. needForGapsConfigNR and needForGapsConfigNR2 andneedForGapsConfigNR3 can be included in RRCReconfiguration message or inRRCResume message. musim-AssistanceConfig and needForType6GapConfig canbe included in otherConfig in RRCReconfiguration message.

NeedForGapsConfigNR contains configuration related to the reporting ofmeasurement gap requirement information. needForGapsConfigNR includes arequestedTargetBandFilterNR. The requestedTargetBandFilterNR indicatesthe target NR bands that the UE is requested to report the gaprequirement information. The requestedTargetBandFilterNR consists of oneor more frequency band indicators.

NeedForGapsConfigNR2 indicates whether UE is allowed to provideNeedForGapsInfoNR2. This IE is enumerated with a single value “True”. Ifthis IE is absent, UE is not allowed to provide NeedForGapsInfoNR2. Ifthis IE is present, UE is allowed to provide NeedForGapsInfoNR2.

NeedForGapsConfigNR3 indicates whether UE is allowed to provideNeedForGapInfoNR3. This IE is enumerated with a single value “True”. Ifthis IE is absent, UE is not allowed to provide NeedForGapInfoNR3. Ifthis IE is present, UE is allowed to provide NeedForGapInfoNR3.

If RRCReconfiguration message or RRCResume message includesneedForGapInfoNR or if needForGapInfoNR has been setup and has not beenreleased, needForGapsConfigNR2 and needForGapInfoNR3 can be included inthe RRCReconfiguration message or in the RRCResume message.

NeedForType6GapConfig indicates whether UE is configured to request fortype6gap activation/deactivation and to provide preferred type6Gappattern. This IE is enumerated with a single value “True”. If this IE isabsent, UE is not configured to provide preferred type6Gap pattern (orpreference on type6Gap). If this IE is present, UE is configured toprovide preferred type6Gap pattern(or preference on type6Gap).

Musim-AssistanceConfig includes a gapRequestProhibitTimer field. thegapRequestProhibitTimer is enumerated with values. Each valuecorresponds to length of duration in a unit of seconds.

In 2A-15, UE checks whether gap-request is needed. UE generates gaprequest information if so.

UE consider itself to be configured to provide the measurement gaprequirement information of NR target bands, if the RRCReconfigurationmessage includes the needForGapInfoNR and if needForGapInfoNR is set tosetup.

UE consider itself to be configured to provide the measurement gaprequirement information of NR target bands, if the RRCResume messageincludes the needForGapInfoNR and if needForGapInfoNR is set to setup.

Condition-group-1 is fulfilled, if the RRCReconfiguration message wasreceived via SRB1 but not within mrdc-SecondaryCellGroup or E-UTRARRCConnectionReconfiguration or E-UTRA RRCConnectionResume, and if theUE is configured to provide the measurement gap requirement informationof NR target bands, and if the RRCReconfiguration message includes theneedForGapsConfigNR.

Condition-group-2 is fulfilled if the RRCResume message includes theneedForGapsConfigNR.

If condition-group-1 is fulfilled or condition-group-2 is fulfilled, UEinclude the needForGapsInfoNR in the second RRC message and set thecontents as follows:

UE includes intraFreq-needForGap and set the gap requirement informationof intra-frequency measurement for each NR serving cell. UE sets eithergap or no-gap for each serving cell.

UE includes an entry in interFreq-needForGap and set the gap requirementinformation for that band if requestedTargetBandFilterNR is configured,for each supported NR band that is also included inrequestedTargetBandFilterNR. UE sets either gap or no-gap for eachsupported NR band.

If condition-group-1 is fulfilled and the RRCReconfiguration messageincludes needForGapsInfoNR2, or if condition-group-2 is fulfilled andthe RRCResume message includes needForGapsInfoNR2, UE includes theneedForGapsInfoNR2 in the second RRC message and set the contents asfollows:

The second RRC message is RRCReconfigurationComplete ifcondition-group-1 was fulfilled. The second message is RRCResumeCompleteif condition-group-2 was fulfilled.

UE includes intraFreq-needForGap2 and set the interruption requirementinformation (i.e., whether ncsg is required) of intra-frequencymeasurement for each NR serving cell. UE sets either ncsg or no-ncsg foreach serving cell.

UE includes an entry in interFreq-needForGap2 and set the interruptionrequirement information for that band if requestedTargetBandFilterNR isconfigured, for each supported NR band that is also included inrequestedTargetBandFilterNR. UE sets either ncsg or no-nscg for eachsupported NR band.

If condition-group-1 is fulfilled and if the RRCReconfiguration messageincludes needForGapsInfoNR3 and if only one serving cell is configuredto the UE (i.e., UE is not configured with carrier aggregation; UE isconfigured with single carrier) as consequence of reconfiguration, UEincludes the needForGapsInfoNR3 in the second RRC message and set thecontents as follows:

UE includes bwpNeedForGap and set the gap requirement information foreach DL BWP of PCell (or SpCell).

If condition-group-2 is fulfilled and if the RRCResume message includesneedForGapsInfoNR3 and if only one serving cell is configured to the UE(i.e., UE is not configured with carrier aggregation; UE is configuredwith single carrier) as consequence of RRC connection resumption, UEincludes the needForGapsInfoNR3 in the second RRC message and set thecontents as follows:

UE includes bwpNeedForGap and set the gap requirement information foreach DL BWP of PCell (or SpCell).

UE consider itself to be configured to provide MUSIM assistanceinformation, if the received otherConfig includes musim-AssistanceConfigand if musim-AssistanceConfig is set to setup.

If UE is configured to provide MUSIM assistance information and if UEneeds the Type5Gap, UE initiate transmission of UEAssistanceInformationas follows:

If UE has a preference for Type5Gap, UE includes musim-GapRequestList inthe UEAssistanceInformation.

If UE determines that type6Gap request is needed, UE generates a type6request MAC CE. The type6 request MAC CE can includes an information onratio between the length of type6Gap and the repetition period oftype6Gap. If transmission power sum should be decreased a lot, higherratio is reported.

Alternatively, if UE is configured to provide its preference on type6Gapand if the UE did not transmit a UEAssistanceInformation withtype6Gap-Preference since it was configured to provide its preference ontype6Gap information, UE initiates transmission ofUEAssistanceInformation.

If UE is configured to provide its preference on type6Gap and if the UEtransmitted a UEAssistanceInformation with type6Gap-Preference since itwas configured to provide its preference on type6Gap and if the currenttype6Gap preference is different from the one indicated in the lasttransmission of the UEAssistanceInformation, UE initiates transmissionof UEAssistanceInformation.

If UE is configured to provide its preference on type6Gap and if the UEtransmitted a UEAssistanceInformation with type6Gap-Preference since itwas configured to provide its preference on type6Gap and if type6Gap isnot required, UE initiates transmission of UEAssistanceInformation.

If transmission of the UEAssistanceInformation message is initiated toprovide preference on type6Gap, UE includes Type6Gap-Preference IE inthe UEAssistanceInformation.

If Type6Gap is required, UE includes a Type6Gap-bitmap in theType6Gap-Preference IE.

If Type6Gap is not required, UE does not include a Type6Gap-bitmap inthe Type6Gap-Preference IE.

UE transmits the UEAssistanceInformation to the base station.

NeedForGapsInfoNR consists of intraFreq-needForGap andinterFreq-needForGap. NeedForGapsInfoNR is used to indicate themeasurement gap requirement information of the UE for NR target bands.

IntraFreq-needForGap field includes NeedForGapsIntraFreqlist IE. Thisfield indicates the measurement gap requirement information for NRintra-frequency measurement.

NeedForGapsIntraFreqlist consists of one or more NeedForGapsIntraFreq.NeedForGapsIntraFreq consists of servCellId and gapindicationIntra.servCellId indicates the serving cell which contains the target SSB(associated with the initial DL BWP) to be measured. gapindicationIntraindicates whether measurement gap is required for the UE to performintra-frequency SSB based measurements on the concerned serving cell.“gap” indicates that a measurement gap is needed if any of the UEconfigured BWPs do not contain the frequency domain resources of the SSBassociated to the initial DL BWP. “no-gap” indicates a measurement gapis not needed to measure the SSB associated to the initial DL BWP forall configured BWPs.

InterFreq-needForGap field includes NeedForGapsBandlistNR. This fieldindicates the measurement gap requirement information for NRinter-frequency measurement.

NeedForGapsBandlistNR consists of one or more NeedForGapsNR.NeedForGapsNR consists of bandNR and gapindication. bandNR indicates theNR target band to be measured. gapindication indicates whethermeasurement gap is required for the UE to perform SSB based measurementson the concerned NR target band while NR-DC or NE-DC is not configured.The UE determines this information based on the resultant configurationof the RRCReconfiguration or RRCResume message that triggers thisresponse. Value gap indicates that a measurement gap is needed, valueno-gap indicates a measurement gap is not needed.

NeedForGapsInfoNR2 consists of intraFreq-needForGap2 andinterFreq-needForGap2. NeedForGapsInfoNR2 is used to indicate theinterruption requirement information of the UE for NR target bands.Alternatively, this IE is used to indicate type4Gap (i.e., networkcontrolled small gap) requirement information of the UE for NR targetbands.

IntraFreq-needForGap2 field includes one or more gapindication2 IEs.Each of one or more gapindication2 IE in intraFreq-needForGap2 indicatesthe interruption requirement (or type4Gap requirement) information forNR intra-frequency measurement with respect to a specific serving cell.

interFreq-needForGap2 field includes one or more gapindication2 IEs.Each of one or more gapindication2 IE in interFreq-needForGap2 indicatesthe interruption requirement (or type4Gap requirement) information forNR inter-frequency measurement with respect to a specific frequencyband.

Gapindication2 is enumerated with three values: “gap” and “ncsg” and“nogap-noncsg”.

If gapIndication2 is set to “ncsg”for a serving cell, ncsg (or type4Gap)is required for the UE to perform intra-frequency SSB measurement on theconcerned serving cell.

If gapIndication2 is set to “ncsg” for a frequency band, ncsg (ortype4Gap) is required for the UE to perform SSB based measurement on theconcerned target band.

If gapIndication2 is set to “gap”for a serving cell, type1Gap ortype2Gap or type3Gap is required for the UE to perform intra-frequencySSB measurement on the concerned serving cell.

If gapIndication2 is set to “gap” for a frequency band, type1Gap ortype2Gap or type3Gap is required for the UE to perform SSB basedmeasurement on the concerned target band.

If gapIndication2 is set to “nogap-noncsg”for a serving cell, neithertype1Gap nor type2Gap nor type3Gap nor type4Gap is required for the UEto perform intra-frequency SSB measurement on the concerned servingcell.

If gapIndication2 is set to “nogap-noncsg” for a frequency band, neithertype1Gap nor type2Gap nor type3Gap nor type4Gap is required for the UEto perform SSB based measurement on the concerned target band.

NeedForGapsInfoNR3 consists of a bwpNeedForGap. NeedForGapsInfoNR3 isused to indicate the measurement gap requirement information of DL BWPsconfigured for the UE.

BWPNeedForGap field includes a BIT STRING. The size of the BIT STRING isequal to the number of DL BWPs configured for the UE in the PCell.Alternatively, the size of the BIT STRING is fixed to a specific valuesuch as 4.

The leading/leftmost bit (bit 0) corresponds to the DL BWP with lowestindex (or BWP 0). The next bit corresponds to the DL BWP with nextlowest index (or BWP 1) and so on. Value 1 indicates type2Gap isrequired for the UE to perform measurement in the corresponding DL BWP.Value 0 indicates type2Gap is not required for the UE to performmeasurement in the corresponding DL BWP. The measurement can beintra-frequency measurement based on SSB or intra-frequency measurementbased on CSI-RS.

Musim-GapRequestList consists of MUSIM-GapRequestList IE. This IEindicate the MUSIM gap (i.e., type5Gap) requirement information.

MUSIM-GapRequestList IE includes one or two or threeMUSIM-GapRequestInfo IE. The reason to limit to three in maximum isbecause configuring a single aperiodic gap and two periodic gaps is acommon scenario with consideration of MUSIM gap usage.

MUSIM-GapRequestInfo includes RequestedMusim-GapType andRequestedMusim-GapOffset and RequestedMusim-GapLength andRequestedMusim-GapRepetitionPeriod and RequestedMusim-GapNumber.

RequestedMusim-GapType is enumerated with a single value of “aperiodic”.If this IE is present in MUSIM-GapRequestInfo and this IE indicates“aperiodic”, aperiodic musim-gap is required. If this IE is absent inMUSIM-GapRequestInfo, periodic musim-gap is required.

Alternatively, RequestedMusim-GapType is enumerated with a single valueof “periodic”. If this IE is present in MUSIM-GapRequestInfo and this IEindicates “periodic”, periodic musim-gap is required. If this IE isabsent in MUSIM-GapRequestInfo, aperiodic musim-gap is required.

Alternatively, if RequestedMusim-GapRepetitionPeriod is present inMUSIM-GapRequestInfo, periodic musim-gap is required. If this IE isabsent in MUSIM-GapRequestInfo, aperiodic musim-gap is required.

Alternatively, if RequestedMusim-GapRepetitionPeriod inMUSIM-GapRequestInfo is set to a specific value like 0, aperiodicmusim-gap is required. If

RequestedMusim-GapRepetitionPeriod in MUSIM-GapRequestInfo is set toother value, periodic musim-gap is required.

Alternatively, if RequestedMusim-GapNumber is present inMUSIM-GapRequestInfo, aperiodic musim-gap is required. If this IE isabsent in MUSIM-GapRequestInfo, periodic musim-gap is required.

RequestedMusim-GapOffset1 and RequestedMusim-GapOffset2 indicate thepreferred musim-Gap starting time point.

RequestedMusim GapLength1 and RequestedMusim-GapLength2 indicate thepreferred musim-Gap length.

RequestedMusim-GapRepetitionPeriod1 andRequestedMusim-GapRepetitionPeriod2 indicate the preferred repetitionperiod.

RequestedMusim-GapNumber indicates the preferred number of aperiodicmusim-Gap.

If the requested gap is periodic gap, RequestedMusim-GapOffset1 andRequestedMusim-GapLength1 and RequestedMusim-GapRepetitionPeriod1 areincluded.

If the requested gap is aperiodic gap, RequestedMusim-GapOffset2 andRequestedMusim-GapLength2 and RequestedMusim-GapRepetitionPeriod2 andRequestedMusim-GapNumber are included.

RequestedMusim-GapOffset1 is an integer between 0 and 159.RequestedMusim-GapOffset2 is an integer between 0 and 10239.

RequestedMusim-GapLength1 is enumerated with eight values: msldot5, ms3,ms3dot5, ms4, ms5dot5, ms6, ms10, ms20.

RequestedMusim-GapLength2 is enumerated with four values: ms32, ms64,ms128, ms256.

RequestedMusim-GapRepetitionPeriod1 is enumerated with four values:ms20, ms40, ms80, ms160.

RequestedMusim- GapRepetitionPeriod2 is enumerated with four values:ms64, ms128, ms256, ms512.

RequestedMusim-GapRepetitionPeriod1 is enumerated with four values: one,two, four, eight.

Type6Gap-Preference IE may include Type6Gap-bitmap IE or may include nosub-level IE.

The Type6Gap-bitmap is 4bit. Each bit corresponds to a specific Type6Gappattern. The first bit corresponds to a first Type6Gap pattern, thesecond bit corresponds to a second

Type6Gap pattern and so on. Each of the first Type6Gap pattern and thesecond Type6Gap pattern and the third Type6Gap pattern is associatedwith a specific gap length and a specific gap repetition periodicityrespectively.

The fourth Type6Gap pattern is associated with two gap lengths. Thefirst gap length is applicable when the SCS of the active UL BWP of afirst cell is 15 KHz or 30 KHz and the second gap length is applicablewhen the SCS of the active UL BWP of a first cell is 60 KHz or 120. Thefist cell is the SpCell of the UE. The first cell could be the servingcell with the shortest SCS among the configured serving cells in FR2.The first cell could be the serving cell with the longest SCS among theconfigured serving cells in FR2.

UE determines which type6Gap is required based on uplink transmissionpower situation and sets the corresponding bit accordingly.

In 2A-17, UE transmits GNB second RRC message.

If the first RRC message was RRCResume message, the second RRC messageis RRCResumeComplete message. The RRCResumeComplete message can includeeither NeedForGapsInfoNR or NeedForGapsInfoNR and NeedForGapsInfoNR2 orNeedForGapsInfoNR and NeedForGapsInfoNR3.

If the first RRC message was RRCReconfiguration message, and if UEconsider itself to be configured to provide the measurement gaprequirement information, the second RRC message isRRCReconfigurationComplete message. The RRCReconfigurationCompletemessage can include either NeedForGapsInfoNR or NeedForGapsInfoNR andNeedForGapsInfoNR2 or NeedForGapsInfoNR and NeedForGapsInfoNR3.

If the first RRC message was RRCReconfiguration message, and if UEconsider itself to be configured to provide MUSIM assistance informationor configured to provide its preference on type6Gap , the second RRCmessage is UEAssistanceInformation message.

The RRCReconfigurationComplete message includes sametransaction-identifier as the transaction-identifier included inRRCReconfiguration message.

The RRCResumeComplete message includes same transaction-identifier asthe transaction-identifier included in RRCResume message.

UEAssistanceInformation message does not include transaction-identifier.

GNB receives the second message and determines gap configurations forthe UE.

In 2A-19, GNB transmits UE third RRC message to indicate gapconfiguration.

The third message can be RRCReconfiguration message.

To configure Type1Gap or Type2Gap or Type3Gap or Type4Gap, GNB includes

MeasConfig IE in the RRCReconfiguration message. The MeasConfig IEspecifies measurements to be performed by the UE. The MeasConfig IEincludes measGapConfig IE.

MeasGapConfig IE may include following fields: a gapFR2 field, a gapFR1field, a gapUE field, a gapUEToAddModList field, a gapUEToReleaseListfield, a gapFR1ToAddModList field, gapFR1ToReleaseList field,gapFR2ToReleaseList field and a gapFR2ToAddModList field

GapFR2 and gapFR1 and gapUE are defined as SetupRelease. If gapFR2(orgapFR1 or gapUE) is set to “setup”, a gapConfig IE is included in thegapFR2(or gapFR1 or gapUE) and a FR2-gap (or FR1-gap or UE-gap) issetup. If gapFR2(or gapFR1 or gapUE) is set to “release”, correspondinggapConfig is released.

GapUEToReleaseList and gapFR1ToReleaseList and gapFR2ToReleaseListconsist of one or moreone or more MeasGapId IEs. gapUEToAddModList andgapFR1ToAddModList and gapFR2ToAddModList consist of one or moreGapConfig IEs. gapUE and gapFR1 and gapFR2 consist of a GapConfig IE.

GapUEToAddModList and gapUE configure one or more per-UE measurementgap. gapFR1ToAddModList and gapFR1 configure one or more per-FR1measurement gap. gapFR2ToAddModList and gapFR2 configure one or moreper-FR2 measurement gap.

During per-UE measurement gaps, UE does not conductreception/transmission from/to the NR serving cells across FR1 and FR2except the reception of signals used for RRM measurement(s), PRSmeasurement(s) and the signals used for random access procedure.

During per-FR1 measurement gaps, UE does not conductreception/transmission from/to the FR1 NR serving cells except thereception of signals used for RRM measurement(s), PRS measurement(s) andthe signals used for random access procedure.

During per-FR2 measurement gaps, UE does not conductreception/transmission from/to the FR2 NR serving cells except thereception of signals used for RRM measurement(s), PRS measurement(s) andthe signals used for random access procedure.

GapFR2 and gapFR1 and gapUE are used to configure a type1Gap.gapUEToAddModList and gapFR1ToAddModList and gapFR2ToAddModList are usedto configure one or more type2Gap or type3Gap or type4Gap or combinationof them.

GapFR2 is located in the non-extended part of the MeasGapConfig. gapFR1and gapUE are located in the first extended part of the MeasGapConfig.gapUEToAddModList and gapFR1ToAddModList and gapFR2ToAddModList arelocated in the second extended part of the MeasGapConfig.

One or moreone or moregapUEToAddModList one or moregapUEToAddModListgapUEToAddModList

A gapConfig IE indicates the time pattern of the gap and the type of thegap. A gapConfig IE includes measGapId and gapOffset and mgl and mgrpand mgta and mgl2 and type2Indicator and type4Indicator anddeactivateIndicator

MGL2 is included in the second extended part of gapConfig IE.type2Indicator and type4Indicator and deactivateIndicator are includedin the third extended part of gapConfig IE. The third extended part isplaced after the second extended part in the gapConfig IE.

GapOffset indicates an integer between 0 and 159 (i.e., highest mgrp-1).

MGL is enumerated with six values: msldot5 and ms3 and ms3dot5 and ms4and ms5dot5 and ms6. value msldot5 corresponds to 1.5 ms. value 3mscorresponds to 3 ms and so on.

MGL2 is enumerated with two values: ms10 and ms20. mgl and mgl2 indicatethe length of gap. If both mgl and mgl2 are included in a gapConfig,mgl2 is applied and mgl is ignored.

Mmgrp is enumerated with four values: ms20, ms40, ms80 and ms160.

Mgta IE is enumerated with three values: ms0, ms0dot25 and ms0dot5. mgtaIE indicates the measurement gap timing advance (or interruption timingadvance in case of Type4Gap) in ms.

Type4Indicator is enumerated with a single value of “True”. If this IEis present in the GapConfig, GapConfig is the configuration of type4Gap.

Type2Indicator is enumerated with a single value of “True”. If this IEis present in the GapConfig, GapConfig is the configuration of type2Gap.

DeactivateIndicator is enumerated with a single value of “Deactivated”.If this IE is present in the GapConfig, the gap is deactivated uponconfiguration. If this IE is absent in the GapConfig for type3Gap or fortype4Gap, the gap is activated upon configuration. this IE is used onlyfor type3Gap or type4Gap and not used for type2Gap.

If a GapConfig includes neither type4Indicator nor type2Indicator,GapConfig is the configuration of type3Gap.

A GapConfig does not include type2Indicator and deactivateIndicator atthe same time. A GapConfig can include type4Indicator anddeactivateIndicator at the same time.

MeasGapIdA measGapIdIE is an integer between 0 and 15. A measGapIdidentifies a measurement gap configuration of a type2Gap or a type3Gapor a type4Gap. Hence different measGapId is allocated across the typesof measurement gaps and frequency regions of measurement gaps (i.e. aper-FR1 type3Gap and a per-FR2 type3Gap shall be allocated withdifferent measGapId).

GapConfig IE included in gapFR2 field or in gapFR1 field or in gapUEfield does not include measGapId IE. GapConfig IE included ingapUEToAddModList or gapFR1ToAddModList or gapFR2ToAddModList caninclude measGapId field.

To configure Type5Gap, GNB includes musim-GapConfig IE in theRRCReconfiguration message. musim-GapConfig IE indicates the gapconfiguration of Type5Gap that applies to all frequencies. amusim-GapConfig IE includes a single musim-GapToReleaseList IE and asingle musim-GapToAddModList IE. A musim-GapToReleaseList consists ofone or more musim-GapId. A musim-GapToAddModList consists of one or moremusim-GapToAddMod IEs.

A musim-GapToAddMod IE can include musim-gapId,musim-Starting-SFN-AndSubframe, musim-GapLength andmusim-GapRepetitionAndOffset.

A musim-gapId IE is an integer between 0 and 1.

Musim-Starting-SFN-AndSubframe IE indicates the gap starting positionfor the aperiodic type5 gap. It includes starting SFN and startingsubframe.

Musim-GapRepetitionAndOffset indicates the gap repetition period in msand gap offset in number of subframes. It includes an integer chosenfrom a integer set. The highest value of the integer set is equal to therepetition period-1. The integer indicates the starting offset of thegap. For example, a integer chosen from a integer set with highest valueof 1279 indicates that the repetition period is 1280 ms. UE determinesthe offset based on the signaled integer and the repetition period basedon the highest integer of the integer set.

If musim-gap is periodic gap, musim-GapLength andmusim-GapRepetitionAndOffset are present.

If musim-gap is aperiodic gap, musim-Starting-SFN-AndSubframe ispresent.

To configure Type6Gap, GNB includes Type6GapConfig IE in theRRCReconfiguration message. Type6GapConfig IE indicates the gapconfiguration of Type6Gap that applies to a specific FR (i.e. FR2).Type6GapConfig IE includes a gapOffset field and a ugl field and a ugrpfield.

UGL field indicates one of ms0dot125 and ms0dot25 and ms0dot5 and ms1.ms0dot125 corresponds to 0.125 ms, ms0dot25 corresponds to 0.25 ms andso on. ugl indicates a length of the type6 gap.

Ugrp field indicates the gap repetition period of the type6 gap. ugrpfield indicates one of ms5 and ms20 and ms40 and ms160.

Type6GapRefServCellIndicator field indicates a serving cell identifierwhose SFN and subframe is used for type6Gap calculation for gap pattern.If this field is absent, UE uses PCell for this purpose.

In 2A-21, UE setup the gap based on the gap information received in2A-17.

If the third message includes measGapConfig IE, UE determines the gap tobe setup according to the information included in the measGapConfig IEas shown in the table below.

TABLE 5 when the conditions are fulfilled, UE setup Conditions forType1Gap determination following gap If measGapConfig includes gapFR1and if gapFR1 UE setup FR1 type1Gap is set to setup and if the GapConfigdoes not include the third extended part If measGapConfig includesgapFR1 and if gapFR1 UE release FR1 type1Gap is set to release and ifthe established gapFR1 is FR1 type1Gap If measGapConfig includes gapFR2and if gapFR2 UE setup FR2 type1Gap is set to setup and if the GapConfigdoes not include the third extended part If measGapConfig includesgapFR2 and if gapFR2 UE release FR2 type1Gap is set to release and ifthe established gapFR2 is FR2 type1Gap If measGapConfig includes gapUEand if gapUE UE setup UE type1Gap is set to setup and if the GapConfigdoes not include the third extended part If measGapConfig includes gapUEand if gapFR2 UE release UE type1Gap is set to release and if theestablished gapUE is UE type1Gap

TABLE 6 when the conditions Conditions for Type2Gap determination arefulfilled If measGapConfig includes a gapFR1ToAddModList and if UE setupPer-FR1 type2Indicator is included (or set to TRUE) in at least onetype2Gap for the gapConfig in the list corresponding measGapId IfmeasGapConfig includes gapFR1ToReleaseList and if at UE release Per-FR1least one measGapId in the list is associated with Per-FR1 type2Gapcorresponding to type2Gap the measGapId If measGapConfig includes agapFR2ToAddModList and if UE setup Per-FR2 type2Indicator is included(or set to TRUE) for at least one type2Gap for the gapConfig in the listcorresponding measGapId If measGapConfig includes gapFR2ToReleaseListand if at UE release Per-FR2 least one measGapId in the list isassociated with Per-FR2 type2Gap corresponding to type2Gap the measGapIdIf measGapConfig includes a gapUEToAddModList and if UE setup UEtype2Gap for type2Indicator is included (or set to TRUE) for at leastone the corresponding gapConfig in the list measGapId If measGapConfigincludes gapUEToReleaseList and if at UE release UE type2Gap least onemeasGapId in the list is associated with UE corresponding to thetype2Gap measGapId

TABLE 7 when the conditions are Conditions for Type3Gap determinationfulfilled If measGapConfig includes a gapFR1ToAddModList UE setupPer-FR1 and if neither type2Indicator nor type4Indicator are type3Gapfor the included in at least one gapConfig in the list correspondingmeasGapId If measGapConfig includes gapFR1ToReleaseList UE releasePer-FR1 and if at least one measGapId in the list is associated type3Gapcorresponding with Per-FR1 type3Gap to the measGapId If measGapConfigincludes a gapFR2ToAddModList UE setup Per-FR2 and if neithertype2Indicator nor type4Indicator are type3Gap for the included in atleast one gapConfig in the list corresponding measGapId If measGapConfigincludes gapFR2ToReleaseList UE release Per-FR2 and if at least onemeasGapId in the list is associated type3Gap corresponding with Per-FR2type3Gap to the measGapId If measGapConfig includes a gapUEToAddModListUE setup UE type3Gap and if neither type2Indicator nor type4Indicatorare for the corresponding included in at least one gapConfig in the listmeasGapId If measGapConfig includes gapUEToReleaseList UE release UEtype3Gap and if at least one measGapId in the list is associatedcorresponding to the with UE type3Gap measGapId

TABLE 8 when the conditions are Conditions for Type4Gap determinationfulfilled If measGapConfig includes a gapFR1ToAddModList UE setupPer-FR1 and if type4Indicator is included in at least one type4Gap forthe gapConfig in the list corresponding measGapId If measGapConfigincludes gapFR1ToReleaseList UE release Per-FR1 and if at least onemeasGapId in the list is associated type4Gap corresponding with Per-FR1type4Gap to the measGapId If measGapConfig includes a gapFR2ToAddModListUE setup Per-FR2 and if type4Indicator is included in at least onetype4Gap for the gapConfig in the list corresponding measGapId IfmeasGapConfig includes gapFR2ToReleaseList UE release Per-FR2 and if atleast one measGapId in the list is associated type4Gap correspondingwith Per-FR2 type4Gap to the measGapId If measGapConfig includes agapUEToAddModList UE setup UE type4Gap and if type4Indicator is includedin at least one for the corresponding gapConfig in the list measGapId IfmeasGapConfig includes gapUEToReleaseList UE release UE type4Gap and ifat least one measGapId in the list is associated corresponding to thewith UE type4Gap measGapId

TABLE 9 when the conditions are Conditions for Type5Gap determinationfulfilled If musim-GapConfig includes musim- UE setup periodic UEGapToAddModList and if musim-GapLength type5Gap for the andmusim-GapRepetitionAndOffset are corresponding musim- included in atleast one musim- gapId. GapConfigToAddMod If musim-GapConfig includesmusim- UE setup aperiodic UE GapToAddModList and if musim-Starting-type5Gap for the SFN-AndSubframe is included in at least correspondingmusim- one musim-GapConfigToAddMod gapId. If musim-GapConfig includesmusim- UE release UE type5Gap GapToReleaseList and if at least onecorresponding to musim- musim-gapId is included in the list gapId.

TABLE 10 when the conditions Conditions for Type6Gap determination arefulfilled If type6GapConfig is included in RRCReconfiguration and UEsetup type6Gap if type6GapConfig is set to setup If type6GapConfig isincluded in RRCReconfiguration and UE release type6Gap if type6GapConfigis set to release

FR1 type1Gap and FR2 type1Gap and UE type1Gap and UE type2Gap and FR1type3Gap and FR2 type3Gap and UE type3Gap and FR1 type4Gap and FR2type4Gap and UE type4Gap are established as below.

UE setup the gap configuration indicated by the measGapConfig inaccordance with OFFSET, i.e., the first subframe of each gap occurs atan SFN and subframe meeting the following condition:

SFN mod T=FLOOR(OFFSET/10);

subframe=gapOffset mod 10;

with T=mgrp/10;

UE apply the specified timing advance mgta to the gap occurrencescalculated above (i.e., the UE starts the measurement mgta ms before thegap subframe occurrences).

Periodic Type5Gap is established as below.

UE setup the gap configuration indicated by the musim-GapConfig inaccordance with the received musim-GapRepetitionAndOffset-, i.e., thefirst subframe of each gap occurs at an SFN and subframe meeting thefollowing condition:

SFN mod T=FLOOR(INTEGER1-/10);

subframe=gapOffset mod 10;

with T=MUSIM-PERIODICITY/10;

INTEGER1 is the integer indicated by musim-GapRepetitionAndOffset.MUSIM-PERIODICITY is equal to the highest value of the correspondinginteger set plus one. The corresponding integer set is the one whereINTEGER1 is chosen.

Aperiodic Type5Gap is established as below.

UE setup the gap configuration indicated by the musim-GapConfig inaccordance with musim-Starting-SFN-AndSubframe, i.e., the first subframeof the aperiodic gap occurs at an SFN and subframe indicated inmusim-Starting-SFN-AndSubframe.

Type6Gap is established as below.

UE setup the gap configuration indicated by the type6GapConfig inaccordance with the received gapOffset, i.e., the first subframe of eachgap occurs at an SFN and subframe meeting the following condition:

SFN mod T=FLOOR(gapOffset/10);

subframe=gapOffset mod 10 if ugrp is larger than 5 ms;

subframe=gapOffset or gapOffset+5 if ugrp is equal to 5 ms;

with T=CEIL(ugrp/10);

Each gap occurs (or begins) at the first static uplink slot determinedfrom the first subframe (i.e., each gap occurs/begins at the firststatic uplink slot starting from the first slot of the first subframe).

As a consequence of above operations, UE setup multiple gapconfigurations. To achieve reasonable level of UE implementationcomplexity, the possible combinations of gaps are limited as below.

TABLE 11 Simultaneous configuration & use (activation) Case 1 n1 *FR1-Type1Gap + n2* FR2-Type1Gap can be configured and usedsimultaneously n1 and n2 are either 0 or 1. Case 2 n3 * UE-Type1Gap canbe configured and used n3 is 1. Case 3 n1 * FR1-Type4Gap +n2*FR2-Type4Gap can be configured and used simultaneously Case 4 n3 *UE-Type4Gap can be configured and used simultaneously Case 5 n4 *FR1-Type3Gap + n5 * FR2-Type3Gap + n6 * UE-Type3Gap can be configuredand used simultaneously. n4 and n5 and n6 are either 0 or 1 or 2. All n4and n5 and n6 being 0 is not valid Case 6 n7 * Type2Gap can beconfigured simultaneously n7 is either 1 or 2 or 3 Only one Type4Gapamong the configured Type4Gap is used Case 7 n8* Type5Gap can beconfigured and used simultaneously n8 is 1 or 2 or 3

All the Type1Gap and Type3Gap and Type4Gap and Type5Gap are immediatelyused (i.e., used from the next occurrence) once the corresponding gapconfigurations are setup.

One or more Type2Gap configuration can be setup. However only subset ofplurality of Type2Gap is used depending on the currently active downlinkBWP.

Only one Type1Gap or only one Type4Gap can be configured and used asFR1-gap. one or two Type3Gap can be configured and used simultaneouslyas FR1-gap.

Only one Type1Gap or only one Type4Gap can be configured as FR2-gap. oneor two Type3Gap can be configured and used simultaneously as FR2-gap.

Only one Type1Gap or only one Type4Gap can be configured and usedsimultaneously as UE-gap. One or more Type2Gap can be configured asUE-gap. One or more Type5Gap can be configured as UE-gap. Only oneType2Gap can be used as UE-gap. One or more Type5Gap can be used asUE-gap simultaneously.

A certain IE (or field) being enumerated with x and y means that the IE(or field) can indicate one of x and y.

In 2A-23, UE applies gap operations during a gap. UE performs normaloperations during non-gap.

TABLE 12 Gap type Applied gap operation Type1Gap Gap Operation 1 duringthe gap Type2Gap Gap Operation 1-1 during the gap Type3Gap Gap Operation1-1 during the gap Type4Gap Gap Operation 2 during interruption lengthGap operation 3 during measurement length Type5Gap Gap Operation 4during the gap Type6Gap Gap Operation 6 during the gap

A gap being active means the relevant gap operation being applied. A gapbeing inactive means the relevant gap operation not being applied andnormal operation being applied as if gap is not configured.

Gap operation comprises data-activity-action-group andnon-data-activity-action-group.

TABLE 13 Gap operation type data-activity-action-groupnon-data-activity-action-group Gap operation 1 Forserving-carrier-group, performing SSB based not performing themeasurement on transmission of HARQ measurement-object- feedback, SR,and CSI group. in the uplink slots and in the uplink symbols of flexibleslots during the gap. not reporting SRS in the uplink slots and in theuplink symbols of flexible slots during the gap. not transmitting on UL-SCH except for Msg3 or the MSGA payload in the uplink slots and in theuplink symbols of flexible slots during the gap. not monitoring thePDCCH in the downlink slots and in the downlink symbols of flexibleslots during the gap except period X. not receiving on DL- SCH in thedownlink slots and in the downlink symbols of flexible slots during thegap except period X. period X is when ra- Response Window or the ra-ContentionResolutionTimer or the msgB-Response Window is running Gapoperation 1-1 same data-activity-action-group performing SSB based asGap operation 1 measurement or CSI- RS based measurement or PRS basedmeasurement on measurement-object- group. Gap operation 2 samedata-activity-action-group RF retuning as Gap operation 1 Gap operation3 For serving-carrier-group, same non-data-activity-action- performingthe group as Gap operation 1-1 transmission of HARQ feedback, SR, andCSI in the uplink slots and in the uplink symbols of flexible slotsduring the gap. reporting SRS in the uplink slots and in the uplinksymbols of flexible slots during the gap. transmitting on UL- SCH in theuplink slots and in the uplink symbols of flexible slots during the gapmonitoring the PDCCH in the downlink slots and in the downlink symbolsof flexible slots during the gap. receiving on DL-SCH in the downlinkslots and in the downlink symbols of flexible slots during the gap. Gapoperation 4 same data-activity-action-group performing paging as Gapoperation 1 reception or system information reception for the other USIMGap operation 6 For serving-carrier-group (i.e. — FR2 serving cells),not performing the transmission of HARQ feedback and CSI during the gap.not reporting SRS during the gap. not transmitting on UL- SCH except forMsg3 or the MSGA payload and except for CG-PUSCH during the gap.performing transmission on PUCCH allocation for SR and on CG- PUSCHresource and PRACH resource

Type 1 gap and type 2 gap and type 3 gap and type 4 gap and type 5 gapconsist with all types of slots (i.e. uplink slots and downlink slotsand flexible slots indicated in tdd-UL-DL-ConfigurationCommon). A type 1gap or a type 2 gap or a type 3 gap or a type 4 gap or a type 5 gap areconsecutive in time within the respective gap (i.e. if the gap length isn ms, the distance between the starting point of the gap and the endpoint of gap is n ms) and consist with consecutive slots.

Type 6 gap consists with only static UL slots indicated intdd-UL-DL-ConfigurationCommon. Type 6 gap could be non-consecutive intime (i.e. if the gap length is n ms, the distance between the startingpoint of the gap and the end point of gap could be longer than n ms) andconsists with slots that could be non-consecutive with each other.

Time span of a gap is between the starting point of the gap and the endpoint of the gap.

During the time span of a type X gap (X is 1 or 2 or 3 or 4), UE is notrequired to (i.e. UE does not) conduct reception/transmission from/tothe corresponding NR serving cells in the corresponding frequency rangeexcept the reception of signals used for RRM measurement(s) and thesignals used for random access procedure.

During the time span of type 6 gap, UE is not required to(i.e. UE doesnot) conduct transmission to the corresponding NR serving cells in FR2except for the signals used for random access procedure, CG-PUSCH (type1 and 2) and PUCCH allocations for SR and LRR. During the time span oftype 6 gap, UE conduct reception from the corresponding NR serving cellin FR2.

Serving-carrier-group and measurement-object-group are determined as intable.

TABLE 14 Gap Type serving-carrier-group measurement-object-groupType1Gap If the gap is FR2 gap, serving- If the gap is FR2 gap,carrier-group is serving carriers (or measurement-object-group is theserving cells) on FR2. measurement objects configured If the gap is FR1gap, serving- for FR2 frequencies. carrier-group is serving carriers (orIf the gap is FR1 gap, serving cells) on FR1. measurement-object-groupis the If the gap is UE gap, serving- measurement objects configuredcarrier-group is all serving carriers for FR1 frequencies. (or servingcells) or serving If the gap is UE gap, measurement- carriers (orserving cells) on FR1 object-group is the measurement and FR2. objectsconfigured for FR1 frequencies and FR2 frequencies. Type2Gap Same asType1Gap Same as Type1 Gap Type3Gap Same as Type1Gap Regardless ofwhether the gap is FR1 gap or FR2 gap or UE gap,measurement-object-group is determined based on the associatedmeasurement objects. If the gap is FR2 gap, only the measurement objectson FR2 can be associated with the gap. If the gap is FR1 gap, only themeasurement objects on FR1 can be associated with the gap. Type4Gap Sameas Type1Gap Same as Type1Gap Type5Gap Type5Gap is UE gap. Type5Gap is UEgap. serving-carrier-group is all serving measurement-object-group isthe carriers (or serving cells) or measurement objects configuredserving carriers (or serving cells) for FR1 frequencies and FR2 on FR1and FR2. frequencies. Type6Gap Type6Gap is FR2 gap N/A (UE is notrequired to perform measurement)

In 2A-25, GNB performs transmission and reception with the UEconsidering the configured gap.

Type2Gap is described in more detail below.

A Type2Gap is associated with a DL BWP according todeactivatedMeasGapList for the DL BWP. A BWP-DownlinkDedicated IE caninclude a deactivatedMeasGapList1 IE.

The deactivatedMeasGapList1 indicates a list of measGapIds where thecorresponding Type2Gaps (i.e. the gaps configured with type2Indicator)are deactivated upon the switch to this BWP.

A SCellConfig IE can include a deactivatedMeasGapList2 IE.

deactivatedMeasGapList2 indicates a list of measGapIds where thecorresponding Type2Gaps (i.e. the gaps configured with type2Indicator)are deactivated while this SCell is activated.

Alternatively, deactivatedMeasGapList2 indicates a list of measGapIdswhere the corresponding Type2Gaps (i.e. the gaps configured withtype2Indicator) are activated while this SCell is deactivated.

One or more Type2gaps can be configured for a UE. Among the gaps, UEactivates a specific gap. The specific gap is the gap determined fromthe deactivatedMeasGapList1 of the active DL BWP or the gap determinedfrom the deactivatedMeasGapList2 of the active SCell. For the active DLBWP, UE deactivates the type2Gaps listed in the deactivatedMeasGapList1and activates the type2Gap not listed in the deactivatedMeasGapList1.For an active SCell, UE deactivates the type2Gaps listed in thedeactivatedMeasGapList2 and activates the type2Gap not listed in thedeactivatedMeasGapList2.

Type2Gap switching occurs when BWP switching occurs. More specifically,BWP switching occurs in the following cases.

Upon configuring Type2Gaps and DL BWPs based on a receivedRRCReconfiguration message, UE activates a Type2Gap determined from thedeactivatedMeasGapList1 of a DL BWP to be activated after RRCreconfiguration. If firstActiveDownlinkBWP is present in theRRCReconfiguration message, the DL BWP to be activated is the DL BWPindicated by firstActiveDownlinkBWP-Id in the RRCReconfigurationmessage. If firstActiveDownlinkBWP-Id is absent in theRRCReconfiguration message, the DL BWP to be activated in the DL BWPthat was active before RRCReconfiguration message is received.

After activating a Type2Gap, UE may need to do gap switching (i.e., UEmay need to deactivate the current active Type2Gap and to activate a newType2Gap). For example, if UE receives uplink grant on PDCCH (DCI format0_1 or 0_2) including a bandwidthpart indicator field indicating an ULBWP different from the current active UL BWP, UE determines that gapswitching is needed if condition 1 and condition 2 are fulfilled.

Condition 1: If the SpCell of the UE is in unpaired spectrum (i.e., TDDspectrum); and

Condition 2: If the active Type2Gap associated with the old DL BWP (DLBWP that is active before reception of the UL grant on PDCCH) isdifferent from the Type2Gap to be activated upon switch to the DL BWPhaving the same BWP id as the UL BWP indicated by the bandwidthpartindicator of the UL grant.

If both conditions are fulfilled, UE deactivates the current Type2Gapand activates the Type2Gap associated with the DL BWP having the sameBWP id as the UL BWP indicated by the bandwidthpart indicator of the ULgrant. If no Type2Gap is associated with the DL BWP, no Type2Gap isactivated.

If UE receives DL assignment on PDCCH (DCI format 1_1 or 1_2), UEdetermines gap switching is needed if condition 3 is fulfilled.

Condition 3: If the active Type2Gap associated with the old DL BWP isdifferent from the Type2Gap to be activated upon switch to the DL BWPindicated by the bandwidthpart indicator of the DL assignment

If condition 3 is fulfilled, UE deactivates the current Type2Gap andactivates the Type2Gap determined from the deactivatedMeasGapList1 ofthe DL BWP indicated by the bandwidthpart indicator of the DLassignment. If deactivatedMeasGapList1 is not configured to the DL BWP,all the configured Type2Gaps are activated.

If the bwp-InactivityTimer associated with the active DL BWP expires, UEdetermines gap switching is needed if condition 4 is fulfilled.

Condition 4: If the active Type2Gap associated with the active DL BWP(old DL BWP) is different from the Type2Gap to be activated upon switchto the DL BWP to be activated

If defaultDownlinkBWP-Id is configured, The DL BWP to be activated isthe DL BWP indicated by the defaultDownlinkBWP-Id.

If defaultDownlinkBWP-Id is not configured, The DL BWP to be activatedis the DL BWP indicated by the initialDownlinkBWP.

If condition 4 is fulfilled, UE deactivates the current Type2Gap andactivates the Type2Gap determined from the deactivatedMeasGapList1 ofthe DL BWP to be activated.

If Random Access procedure is initiated on a serving cell, UE determinesgap switching is needed if condition 5 and condition 6 are fulfilled.

Condition 5: If PRACH occasions are not configured for the active UL BWPand if the serving cell is SpCell

Condition 6: If the active Type2Gap associated with the active DL BWP(old DL BWP) is different from the Type2Gap to be activated upon switchto the DL BWP indicated by initialDownlinkBWP.

If condition 5 and 6 are fulfilled, UE deactivates the current Type2Gapand activates the Type2Gap associated with the DL BWP indicated byinitialDownlinkBWP. If no Type2Gap is associated with the initial DLBWP, no Type2Gap is activated.

Alternatively, a BWP-DownlinkDedicated IE and a SCellConfig IE caninclude a deactivatedMeasGapBitmap IE respectively.

Each bit of the deactivatedMeasGapBitmap indicates the Type2GapStatus ofeach type2Gap.

One UE-Type2gap or one FR1-Type2gap or one FR2-Type2gap or oneFR1-Type2gap and one FR2-Type2gap can be configured for the UE.

If Type2GapStatus of the active DL BWP of the PCell is set to a firstvalue (e.g., deactivated), UE deactivates the Type2Gap for the PCell.

If Type2GapStatus of the active DL BWP of the PCell is set to a secondvalue (e.g., activated), UE activates the Type2Gap for the PCell.

The other way is also possible.

If Type2GapStatus of the active DL BWP of the PCell is set to a firstvalue (e.g., activated), UE activates the Type2Gap for the PCell.

If Type2GapStatus of the active DL BWP of the PCell is set to a secondvalue (e.g., deactivated), UE deactivates the Type2Gap for the PCell.

The initial DL BWP is the BWP of which BWP-id is 0. The initial DL BWPis the BWP of which BWP-id is implicitly configured. The initial BWP isthe BWP of which BWP-id is not associated with an explicit BWP-Id IE.The initial DL BWP is the BWP of which cell specific configuration isprovided in SIB1 and UE specific configuration is provided inRRCReconfiguration message. DL BWPs other than the initial BWP are theBWP of which cell specific configuration and UE specific configurationare provided in RRCReconfiguration message.

Type2Gap switching occurs when SCell activation/deactivation occurs.Upon configuring Type2Gaps and a SCell based on a receivedRRCReconfiguration message, UE activates a Type2Gap determined from thedeactivatedMeasGapList2 of the SCell.

Upon reception of a first MAC CE activating or deactivating the SCell,UE activates a Type2Gap determined from the deactivatedMeasGapList2 ofthe SCell.

Upon expiry of sCellDeactivationTimer configured for the SCell, UEactivates a Type2Gap determined from the deactivatedMeasGapList2 of theSCell.

Alternatively, upon configuring Type2Gaps and a SCell based on areceived RRCReconfiguration message, UE deactivates one or two Type2Gapdetermined from the deactivatedMeasGapList2 of the SCell.

Upon reception of a MAC CE activating or deactivating the SCell, UEdeactivates one or two Type2Gap determined from thedeactivatedMeasGapList2 of the SCell.

Upon expiry of sCellDeactivationTimer configured for the SCell, UEdeactivates one or two Type2Gap determined from thedeactivatedMeasGapList2 of the SCell.

Type2Gap switching occurs when a second MAC CE activating a Type2Gap isreceived.

Upon receiving the second MAC CE, UE activates the type2Gap indicated inthe second MAC CE.

When BWP switch occurs, which results in status change of Type2Gap (i.e.Type2Gap activation or deactivation or both), UE finishes type2Gapactivation or deactivation within 5+x ms since BWP switch occur (i.e.since DCI reception or timer expiry). x is determined based at leastpart on bwp-SwitchingDelay and SCS of the BWPs as in table below.

TABLE 15 shorter SCS between old BWP and the new BWP slot length Type 1Type 2  15 kHz 1 ms 1 ms 3 ms  30 kHz 0.5 ms 1 ms 2.5 ms  60 kHz 0.25 ms0.75 ms 2.25 ms 120 kHz 0.125 ms 0.75 ms 2.25 ms

BWP-SwitchingDelay defines whether the UE supports DCI and timer basedactive BWP switching delay type1 or type2. It indicates one of type1 andtype2.

When SCell is deactivated due to the first MAC CE reception, UE finishestype2Gap activation or deactivation within 5+y ms since the first MAC CEdeactivating the SCell is received. y is determined based at least parton the timing when acknowledgement for the first MAC CE is transmitted.y is equal to 3+y1 ms, where y1 is the timing between the first MAC CEtransmission and the corresponding acknowledgement.

When SCell is deactivated due to due to the expiry ofsCellDeactivationTimer, UE finishes type2Gap activation or deactivationwithin 5+y2 ms since the expiry of sCellDeactivationTimer. y2 is fixedto 3.

When SCell is activated or deactivated due to reception ofRRCReconfiguration message, UE finishes type2Gap activation ordeactivation within 5+z ms since the RRCReconfiguration message isreceived. z is 10 ms if RRCReconfiguration includes the configuration onPCell and does not includes the configuration on SCell addition/release.z is 16 ms if RRCReconfiguration includes the configuration on SCelladdition/release.

The first MAC CE is SCell Activation/Deactivation MAC CE. The second MACCE is Type2Gap L2 response MAC CE.

Type6Gap is described in more detail below.

The length of the type6Gap in terms of the number of slots is determinedbased on ugl field and type6GapRefServCellIndicator field. UE firstdetermines the number of uplink slots from the gap length indicated bythe ugl field and the SCS of the serving cell indicated bytype6GapRefServCellIndicator. For example, if the gap length is 0.5 msand UL SCS of the reference serving cell is 60 KHz, the number of slotsfor a type6Gap is 2 (=gap length/slot length of the reference servingcell). If type6GapRefServCellIndicator field is absent intype6GapConfig, UE determines the number of uplink slots based on uglfield and the SCS of the active UL BWP of the PCell.

Type6Gap starts in the nearest uplink slot from the referencesubframe(or the first subframe). Type6Gap continues for consecutive nuplink slots. Depending on tdd-UL-DL-ConfigurationCommon, DL slots andflexible slots can exists between uplink slots(or within time span ofuplink slots). Hence the actual length of type6Gap is determined by thenumber of uplink slots derived from type6GapLength field and the numberof downlink slots that exist within the time span of the uplink slotsand the number of flexible slots that exist within the time span of theuplink slots. UE performs normal downlink operation in the downlinkslots and flexible slots within the Type6Gap. UE performs normal uplinkoperation in the flexible slots within the Type6Gap. UE stops any uplinkoperation in the uplink slots within the Type6Gap. UE does not performuplink transmission of FR1 serving cells in the uplink slots during FR1type6Gap. UE does not perform uplink transmission of FR2 serving cellsin the uplink slots during FR2 type6Gap. UE does not perform uplinktransmission of all serving cells in the uplink slots during UEtype6Gap.

If Type2Gap needs to be updated or to be activated with regards tolocation measurement, UE moves to step 2A-27.

In 2A-27, UE transmits and GNB receives a type2Gap activation requestmessage. The message could be either type2Gap L3 request message(type2Gap activation request RRC message) or type2Gap L2 request message(type2Gap activation request MAC CE).

If location measurements towards NR is started and if one or moreType2gaps are configured and if at least one of the type2Gaps meets themeasurement gap requirements, UE trigger type2Gap L2 request procedureto initiate the transmission of the type2Gap related L2 request.

If location measurements towards NR is started and if one or moreType2gaps are configured and if none of the type2Gaps meets themeasurement gap requirements, UE triggers type2Gap L3 request procedureto initiate transmission of the type2Gap L3 request message thatincludes a measurementIndication field set to nr-PRS-Measurement.

If location measurements towards NR is stopped, UE triggers type2Gap L3request procedure to initiate transmission of the type2Gap L3 requestmessage that includes a measruementIndication field set to release.

If at least one type2Gap L2 request is triggered, UE cancel the alreadytriggered type2Gap L2 request message, if any, and triggers new type2GapL2 request message.

If Type2Gap L2 request message has been triggered, and not cancelled andif UL-SCH resources are available for a new transmission and theseUL-SCH resources can accommodate the Type2Gap L2 request message plusits subheader as a result of logical channel prioritization, UE canceltriggered Type2Gap L2 request message and generates the Type2Gap L2request message and.

If Type2Gap L2 request message has been triggered, and not cancelled andif UL-SCH resources are not available for a new transmission UE triggersa Scheduling Request for Type2Gap L2 request message without triggeringBSR.

A Type2Gap L2 request message is identified by MAC subheader withone-octet eLCID and has a fixed size of one octet. A Type2Gap L2 requestmessage consists of a bitmap or of n R bits and a measGapId field. ThemeasGapId field indicates the type2Gap that UE requests for activation.The size of the measGapId field is 8-n bits (or n is 8—the size ofmeasGapId field). Each bit of the bitmap corresponds to a type2Gapconfigured for the UE. The first bit corresponds to the type2Gap withthe lowest measGapId, the second bit corresponds to the type2Gap withthe second lowest measGapId and so on.

The subheader of a Type2Gap L2 request message is consists of two R bitsand a 6 bit LCID field and a 8 bit eLCID field. The LCID field is set toa first value indicating a 8 bit extended logical channel ID fieldfollows. The first value is 34. If LCID field is set to a second value,a 16 bit extended logical channel ID field follows. UE sets the LCIDfield to the first value for Type2Gap L2 request message. 8 bit eLCIDfield is set to a third value indicating that the type of correspondingMAC CE is type2Gap L2 request message. The third value in eLCID fieldcorresponds to the LCID value calculated from the third value plus aconstant. It is to avoid the ambiguity between LCID value indicated byLCID field and LCID value indicated by eLCID field. The constant is themaximum value of LCID field plus one (i.e. 64). For example, if thethird value in eLCID field is 249, it indicates the type of the MAC CEcorresponds to LCID value of 313 (=249+64).

Type2Gap L3 request message includes a measurementIndication field thatcan be set to release or set to setup. If it is set to setup, the fieldincludes a LocationMeasurementInfo IE. The LocationMeasurementInfo IEincludes a dl-PRS-PointA field and RepetitionAndOffset field and aPRS-length field.

DL-PRS-PointA field indicates the absolute radio frequency channelnumber of the carrier for which UE needs to perform PRS measurement.

RepetitionAndOffset field indicates the gap periodicity in ms and offsetin number of subframes of the requested gap.

PRS-length field indicates the gap length of the requested gap.

UE shall set the contents of Type2Gap L3 request message according tothe required gap and trigger BSR to request resource for Type2Gap L3request message. The triggered BSR can trigger SR.

The priority of type2Gap L2 request message is higher than the priorityof type2Gap L3 request message.

The subheader of a Type2Gap L3 request message is consists of one R bitand one F field and a LCID field and a L field. The LDID field is set to1 to indicate that the MAC SDU is SRB1 data.

In 2A-29, GNB transmits and UE receives a type2Gap activation responsemessage.

The message could be either type2Gap L3 response message (type2Gapactivation response RRC message) or type2Gap L2 response message(type2Gap activation response MAC CE). If UE transmitted type2Gap L2request message, GNB respond with type2Gap L2 response message. If UEtransmitted type2Gap L3 request message, GNB respond with type2Gap L3response message.

A Type2Gap L2 response message is identified by MAC subheader withone-octet eLCID and has a variable size. A Type2Gap L2 response messageinclude one or more response information. A response informationincludes a A/D field (n−1) R bits and a measGapId field.

A/D field indicates whether to activate or deactivate the type2Gapindicated by the measGapId following the A/D field. The field is set to1 to indicate activation, otherwise it indicates deactivation.

The subheader of a Type2Gap L2 response message is consists of one R bitand one F field and a LCID field and a 8 bit eLCID field and a L field.The LCID field is set to a first value indicating a 8 bit extendedlogical channel ID field follows. The first value is 34. 8 bit eLCIDfield is set to a fourth value indicating that the type of correspondingMAC CE is type2Gap L2 response message. The fourth value in eLCID fieldcorresponds to the LCID value calculated from the fourth value plus aconstant.

L field indicates the size of Type2Gap L2 response message. The size isdetermined by the number of response information included in themessage.

Upon the reception of the Type2Gap L2 response message, if the messageindicates deactivation of a type2Gap UE deactivates the type2Gap and ifthe message indicates activation of a type2Gap UE activates thetype2Gap.

Since measGapId is consistently allocated across type2Gap and type3Gapand type4Gap, type2Gap L2 response message can activate type3Gap ortype4Gap as well. To activate or deactivate a plurality of type3Gapsassociated with a specific carrier frequency (or a specific measurementobject), GNB includes in type2Gap L2 response message the plurality ofmeasGapId(s). Each of plurality of measGapId(s) is associated with atype3Gap and one or more measGapIds are associated with the samemeasurement object.

Type2Gap L3 response message includes a measGapConfig. The measGapConfigmay include a gapConfig IE corresponding to the requested type2Gap. ThegapConfig IE may include a one bit indication that the type2Gap isactivated.

In 2A-31, UE and GNB performs RRC_CONNECTED operation (e.g. datatransmission/reception) according to the configured and activated gap.

During the RRC_CONNECTED operation, UE may detect some events andinitiates RRC re-establishment procedure. The event includes detectingradio link failure, re-configuration with sync failure, integrity checkfailure and RRC connection reconfiguration failure.

Upon such failures, UE needs to re-establish the RRC connection in thenew cell. To perform this task quickly, UE stops all other tasks likegap request or preference indication. Also, since gap operationrestricts the UE activity, UE stops gap operation as well.

In 2A-33, UE performs RRC re-establishment procedure.

Upon initiation of RRC re-establishment procedure and beforetransmission RRCReestablishmentRequest in the selected suitable cell, UEreleases configuration information for gap request such asneedForGapsConfigNR, needForGapsConfigNR2, needForGapsConfigNR3,musim-AssistanceConfig and needFortype6Gap. UE also cancels anytriggered type2Gap L2 request procedure and discard any type2Gap L2request message.

UE performs cell selection to find a new suitable cell.

Upon selecting a suitable cell, UE applies default MAC Cell Groupconfiguration and CCCH configuration and initiates transmission ofRRCReestablishmentRequest message.

The RRCReestablishmentRequest message includes a ue-Identity field and ashortMAC-I field and a reestablishmentCause field.

UE re-establish PDCP and RLC of SRB1 and transmitsRRCReestablishmentRequest via SRB0.

GNB receives the RRCReestablishmentRequest message and determineswhether to reestablish the RRC connection based on the ue-Identity fieldand the shortMAC-I field and the reestablishmentCause field.

If GNB determines to reestablish RRC connection with the UE, GNBtransmits RRCReestablishment message via SRB1.

UE receives the RRCReestablishment message via SRB1 and release the typex (x is 1 or 2 or 3 or 4) gap configurations indicated by measGapConfigand the type 5 gap configuration indicated by musim-GapConfig and type 6gap configuration indicated by type6GapConfig.

UE transmits to GNB RRCReestablishmentComplete message to confirm thatUE completes the procedure.

In short, UE releases gap request configuration at first point of timeand UE release gap configuration at second point of time. UE can stopgap operation before releasing the configuration to facilitate quickerreestablishment. For example, UE can stop gap operation at first pointof time or at third point of time.

The first point of time is after initiating RRC re-establishmentprocedure and before selecting a suitable cell (or before transmittingRRCReestablishmentRequest message via SRB0).

The second point of time is after receiving RRCReestablishment messagevia SRB1 and before transmitting RRCReestablishmentComplete message viaSRB1.

The third point of time is after transmitting RRCReestablishmentRequestmessage via SRB0 and before receiving RRCReestablishment message viaSRB1.

FIG. 3 is a flow diagram illustrating an operation of a terminal.

In 3a-05, terminal receives a first RRCReconfiguration message, thefirst RRCReconfiguration message includes a first configuration relatedto the reporting of measurement gap requirement information, the firstconfiguration includes a information related to the first gap(type1Gap)requirement reporting and a information related to the secondgap(type4Gap) requirement reporting.

In 3a-10, terminal transmits a UEAssistanceInformation message based atleast in part on the first configuration.

In 3a-15, terminal receives a second RRCReconfiguration message, thesecond

RRCReconfiguration message includes a second configuration, the secondconfiguration includes one or more gap configuration information, thegap configuration information includes a measGapId and a type2Indicatorand a gapOffset and a mgl and a mgrp.

In 3a-20, terminal applies the second configuration in the secondRRCReconfiguration message.

In 3a-25, terminal starts gap operation based at least in part on theone or more gap configuration information in the second configuration.

In 3a-30, terminal initiates RRC re-establishment procedure.

In 3a-35, terminal release the first configuration at a first point oftime and the second configuration at a second point of time.

The first point of time is after the initiation of RRC re-establishmentprocedure and before cell selection. The second point of time is afterreceiving RRCReestablishment message via SRB1 and before transmittingRRCReestablishmentComplete message via SRB1.

In 3a-40, terminal discards a type2Gap L2 request message at a thirdpoint of time and terminal stops the gap operation at a fourth point oftime.

The third point of time is after the initiation of RRC re-establishmentand before the first point of time. The fourth point of time is afterthe initiation of RRC re-establishment procedure and before discardingany type2Gap L2 request message.

FIG. 4A is a block diagram illustrating the internal structure of a UEto which the disclosure is applied.

Referring to the diagram, the UE includes a controller 4A-01, a storageunit 4A-02, a transceiver 4A-03, a main processor 4A-04 and I/O unit4A-05.

The controller 4A-01 controls the overall operations of the UE in termsof mobile communication. For example, the controller 4A-01receives/transmits signals through the transceiver 4A-03. In addition,the controller 4A-01 records and reads data in the storage unit 4A-02.To this end, the controller 4A-01 includes at least one processor. Forexample, the controller 4A-01 may include a communication processor (CP)that performs control for communication and an application processor(AP) that controls the upper layer, such as an application program. Thecontroller controls storage unit and transceiver such that UE operationsillustrated in FIG. 2 and FIG. 3 are performed.

The storage unit 4A-02 stores data for operation of the UE, such as abasic program, an application program, and configuration information.The storage unit 4A-02 provides stored data at a request of thecontroller 4A-01.

The transceiver 4A-03 consists of a RF processor, a baseband processorand one or more antennas. The RF processor performs functions fortransmitting/receiving signals through a wireless channel, such assignal band conversion, amplification, and the like. Specifically, theRF processor up—converts a baseband signal provided from the basebandprocessor into an RF band signal, transmits the same through an antenna,and down—converts an RF band signal received through the antenna into abaseband signal. The RF processor may include a transmission filter, areception filter, an amplifier, a mi10r, an oscillator, adigital-to-analog converter (DAC), an analog-to-digital converter (ADC),and the like. The RF processor may perform MIMO and may receive multiplelayers when performing the MIMO operation. The baseband processorperforms a function of conversion between a baseband signal and a bitstring according to the physical layer specification of the system. Forexample, during data transmission, the baseband processor encodes andmodulates a transmission bit string, thereby generating complex symbols.In addition, during data reception, the baseband processor demodulatesand decodes a baseband signal provided from the RF processor, therebyrestoring a reception bit string.

The main processor 4A-04 controls the overall operations other thanmobile operation. The main processor 4A-04 process user input receivedfrom I/O unit 4A-05, stores data in the storage unit 4A-02, controls thecontroller 4A-01 for required mobile communication operations andforward user data to I/O unit 4A-05.

I/O unit 4A-05 consists of equipment for inputting user data and foroutputting user data such as a microphone and a screen. I/O unit 4A-05performs inputting and outputting user data based on the mainprocessor's instruction.

FIG. 4B is a block diagram illustrating the configuration of a basestation according to the disclosure.

As illustrated in the diagram, the base station includes a controller4B-01, a storage unit 4B-02, a transceiver 4B-03 and a backhaulinterface unit 4B-04.

The controller 4B-01 controls the overall operations of the main basestation. For example, the controller 4B-01 receives/transmits signalsthrough the transceiver 4B-03, or through the backhaul interface unit4B-04. In addition, the controller 4B-01 records and reads data in thestorage unit 4B-02. To this end, the controller 4B-01 may include atleast one processor. The controller controls transceiver, storage unitand backhaul interface such that base station operation illustrated inFIG.2 are performed.

The storage unit 4B-02 stores data for operation of the main basestation, such as a basic program, an application program, andconfiguration information. Particularly, the storage unit 4B-02 maystore information regarding a bearer allocated to an accessed UE, ameasurement result reported from the accessed UE, and the like. Inaddition, the storage unit 4B-02 may store information serving as acriterion to deter mine whether to provide the UE with multi-connectionor to discontinue the same. In addition, the storage unit 4B -02provides stored data at a request of the controller 4B-01.

The transceiver 4B-03 consists of a RF processor, a baseband processorand one or more antennas. The RF processor performs functions fortransmitting/receiving signals through a wireless channel, such assignal band conversion, amplification, and the like. Specifically, theRF processor up—converts a baseband signal provided from the basebandprocessor into an RF band signal, transmits the same through an antenna,and down—converts an RF band signal received through the antenna into abaseband signal. The RF processor may include a transmission filter, areception filter, an amplifier, a mi10r, an oscillator, a DAC, an ADC,and the like. The RF processor may perform a down link MIMO operation bytransmitting at least one layer. The baseband processor performs afunction of conversion between a baseband signal and a bit stringaccording to the physical layer specification of the first radio accesstechnology. For example, during data transmission, the basebandprocessor encodes and modulates a transmission bit string, therebygenerating complex symbols. In addition, during data reception, thebaseband processor demodulates and decodes a baseband signal providedfrom the RF processor, thereby restoring a reception bit string.

The backhaul interface unit 4B-04 provides an interface forcommunicating with other nodes inside the network. The backhaulinterface unit 4B-04 converts a bit string transmitted from the basestation to another node, for example, another base station or a corenetwork, into a physical signal, and converts a physical signal receivedfrom the other node into a bit string.

What is claimed is:
 1. A method by a terminal, the method comprising:receiving, by the terminal from a base station, a firstRRCReconfiguration, the first RRCReconfiguration includes a first gaprequest configuration and a second gap request configuration, the firstgap request configuration is related to a first type gap request and thesecond gap request configuration is related to a second type gaprequest; receiving, by the terminal from the base station, a secondRRCReconfiguration, the second RRCReconfiguration includes a first gapconfiguration and a second gap configuration, the first gapconfiguration includes a configuration for the first type gap and thesecond gap configuration includes a configuration for the second typegap; establishing by the terminal a first gap or a second gap;initiating by the terminal a Radio Resource Control (RRC)re-establishment procedure; releasing, by the terminal, the first gaprequest configuration at a first point of time; and releasing, by theterminal, the first gap configuration and the second gap configurationat a second point of time, wherein the first gap consists of a one ormore static uplink slots, number of the one or more static uplink slotsof the first gap is determined based on the first gap configuration andsubcarrier spacing of active uplink bandwidth part, and wherein thefirst point of time is after initiation of the RRC re-establishmentprocedure and before cell selection, the second point of time is afterreceiving RRCReestablishment message via Signaling Radio Bearer1(SRB1)and before transmitting RRCReestablishmentComplete message via SRB1. 2.A terminal in a wireless communication system, the terminal comprising:a transceiver configured to transmit and receive a signal; and acontroller configured to control the transceiver to: receive from a basestation a first RRCReconfiguration, the first RRCReconfigurationincludes a first gap request configuration and a second gap requestconfiguration, the first gap request configuration is related to a firsttype gap request and the second gap request configuration is related toa second type gap request; receive from the base station a secondRRCReconfiguration, the second RRCReconfiguration includes a first gapconfiguration and a second gap configuration, the first gapconfiguration includes a configuration for the first type gap and thesecond gap configuration includes a configuration for the second typegap; establish a first gap or a second gap; initiate a Radio ResourceControl (RRC) re-establishment procedure; release the first gap requestconfiguration at a first point of time; and release the first gapconfiguration and the second gap configuration at a second point oftime, wherein the first gap consists of a one or more static uplinkslots, number of the static uplink slots of the first gap is determinedbased on the first gap configuration and subcarrier spacing of activeuplink bandwidth part, and wherein the first point of time is afterinitiation of the RRC re-establishment procedure and before cellselection, the second point of time is after receivingRRCReestablishment message via Signaling Radio Bearer1(SRB1) and beforetransmitting RRCReestablishmentComplete message via SRB1.